Why users choose this
Connect Continue.dev to AgentID over MCP to call its tools and retrieve project context from shared memory.
What AgentID adds
AgentID MCP toolsShared memory accessPortable profileOne handle across multiple MCP clients
Best used when
- Keep Continue.dev aligned to one durable handle across projects, repos, and machines.
- Retrieve a project decision from shared memory in a new Continue.dev session.
- Move between multiple MCP-compatible tools without rebuilding the same agent by hand.
Setup flow
How Continue.dev connects
Use this as the high-level integration path. The exact clicks depend on the product UI, but the AgentID role stays the same: one canonical agent above the tool.
01
Create or choose the AgentID agent you want this tool to use.
02
Add the AgentID MCP server to Continue.dev and point it at your handle.
03
Open a new session in Continue.dev, check the connection, and call an AgentID memory tool.
Where this fits
AgentID is most useful here when you want the same handle to show up in multiple tools without maintaining separate prompts, rules, and memory conventions in each one.
Recommended next step
Start by creating the agent first, then plug this integration into that handle instead of configuring its profile inside the tool itself.
See MCP setup →Related integrations
Same connection category, different tool
Claude Code
Connect Claude Code to AgentID over MCP to save project decisions and make them available to Cursor and other connected tools.
Open details →
Claude Desktop
Claude's desktop app. Full MCP support means your handle, memory, and skills arrive automatically when the app starts.
Open details →
Cursor
Connect Cursor to AgentID over MCP to look up project decisions saved by Claude Code and other connected tools.
Open details →
Windsurf
Codeium's agentic IDE. MCP brings your AgentID identity into every wave, repo, and machine without copy-pasting prompts.
Open details →