Use the same context in every tool
Connect more than one AI to Jackdaw — they all read the same current, permission-aware state.
Jackdaw maintains one current operating context that any authorized, MCP-capable AI can read. Connect a second tool and it can use the decisions, constraints, and evidence the team has already established.
For exact Claude Code, Codex, and Cursor setup steps, follow Use one memory across Claude, Codex, and Cursor.
How it works
Every AI you connect points at the same endpoint:
Each one signs in and you grant it access to a workspace. From then on, every connected tool reads the same curated context for that workspace — you set your data up once, in Jackdaw, and your tools read it from there. A direct, nonconflicting fact can save immediately. Review a correction or conflict in the Inbox before the next tool relies on the changed version.
What you can connect today
- Claude.ai — add it as a custom connector. See Make Claude.ai answer like it knows you.
- Claude Code, Codex, and Cursor — install the Jackdaw coding-tool plugin for relevant context and session capture, or connect manually over MCP.
- Any standards-compliant MCP client — Jackdaw is a standard MCP server with OAuth, so other MCP-capable tools connect with the same URL and consent flow.
Why this matters
The point is not merely that context outlives one tool. It is that every authorized tool starts from what the team currently knows: the accepted decision, the superseded history, the evidence, and the boundaries that apply.