Use one memory across Claude, Codex, and Cursor

If you keep retyping your role, project decisions, and preferences when you move between AI tools, put the durable parts in one Jackdaw workspace. Claude.ai can connect over MCP. For Claude Code, Codex, and Cursor, Jackdaw's coding-tool plugin installs context and session capture with one sign-in.

This shares Jackdaw's current context. The plugin can also import Claude Code's repository memory notes or past sessions if you choose. It does not automatically synchronize each tool's native memory with the others.

1. Give them something specific to retrieve

Choose one active project and write a current decision on its Jackdaw Wiki page, with its owner and source if you have them. For example:

“The Northwind launch is paused until the security review is complete. Priya owns the review.”

Check that the page is in the workspace you intend to authorize. Each tool needs access to that same workspace during Jackdaw's sign-in flow.

2. Connect your tools

For Claude.ai and other MCP clients, use this server URL:

https://mcp.jackdaw.so/mcp/

Claude.ai

In Claude → Settings → Connectors, add a custom connector with the server URL above. Sign in to Jackdaw and select your workspace. If your Claude plan or interface does not offer custom connectors, use Claude Code below or another MCP client. The Claude.ai walkthrough has the full setup.

Claude Code, Codex, and Cursor

The Jackdaw coding-tool plugin is the shortest setup for these three tools. Download its installer in Jackdaw, run it in your repository, sign in, and choose the same workspace. It supplies relevant context and captures finished session turns. For Claude Code, setup offers an optional import of existing repository memory notes and a choice to turn native auto-memory off.

If you prefer a manual MCP-only connection, use the commands below. MCP lets the model pull context when it calls a tool; the plugin also supplies context and captures sessions.

Claude Code

To make Jackdaw available across your Claude Code projects, run:

claude mcp add --transport http --scope user jackdaw https://mcp.jackdaw.so/mcp/
claude mcp list

In Claude Code, use /mcp to complete or check the Jackdaw sign-in. The plugin can put relevant context into prompts automatically; MCP remains available for a deeper, question-specific pull.

Codex

Add the server from the Codex CLI (its MCP configuration is shared with the Codex IDE extension):

codex mcp add jackdaw --url https://mcp.jackdaw.so/mcp/
codex mcp list

Complete Jackdaw's sign-in when Codex asks you to authenticate the server. Select the same workspace. Once connected, Codex can call get_context during a task.

Cursor

For a connection available in all your local Cursor projects, create or update ~/.cursor/mcp.json:

{
  "mcpServers": {
    "jackdaw": {
      "url": "https://mcp.jackdaw.so/mcp/"
    }
  }
}

If the file already contains other servers, add only the jackdaw entry inside its existing mcpServers object. In Cursor's Customize → MCP area, authenticate Jackdaw and choose the same workspace. A project-specific connection can instead live in .cursor/mcp.json in that repository.

3. Check the handoff

Start a new session in each connected tool and ask:

“Call Jackdaw's get_context with this question: What is the current Northwind launch decision, and who owns the security review?”

Confirm that the tool called Jackdaw and returned the decision you wrote. Then change the decision on its Jackdaw page and ask again in a new session in another tool. You should see the updated state without retyping the decision there.

If a tool has the server configured but does not call it, ask it explicitly to use get_context with your real question. MCP gives the model a way to pull context; the model still decides when to use a tool. If you state a direct, nonconflicting fact through Jackdaw’s remember tool, it can save immediately. A correction, identity detail, or conflict waits in the Inbox; settle it before expecting other tools to use the new version.

For the tool list and access scopes, see Connect via MCP.

If a client's setup screen has changed, check the current Codex and Claude Code MCP commands and Cursor MCP configuration.