The Inter-Agent Context Bridge - MCP server for shared agent memory
Wormhole MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. The Inter-Agent Context Bridge - MCP server for shared agent memory.
Keep your AI coding agents in sync. Wormhole gives Claude Code, GitHub Copilot, and Cursor a shared memory layer—so when you switch tools mid-task, nothing gets lost.
Once Wormhole is connected, these are the calls the assistant has available:
get_recent — The get_recent tool exposed by this serverget_tags — The get_tags tool exposed by this serversave_knowledge — Persist decisions, pitfalls, conventions, or constraints so agents don’t repeat mistakessearch_project_knowledge — Intent-aware lookup of stored knowledge. Prefers types that match your intentcheck_conflicts — The check_conflicts tool exposed by this serverPerformance — The Performance tool exposed by this servercleanup — // Clean specific session cleanup({ scope: "session", session_id: "abc-123" })start_session — Sessions automatically isolate context—previous events hidden from queriesend_session — The end_session tool exposed by this serverlist_sessions — The list_sessions tool exposed by this serverswitch_session — The switch_session tool exposed by this serverConfiguration — The Configuration tool exposed by this serverThe server ships on npm as wormhole, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Wormhole's toolset — get_recent, get_tags, save_knowledge and 9 more — is a fair guide to whether it matches your workflow. It is maintained by fatmali; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| get_recent | The get_recent tool exposed by this server. |
| get_tags | The get_tags tool exposed by this server. |
| save_knowledge | Persist decisions, pitfalls, conventions, or constraints so agents don’t repeat mistakes. |
| search_project_knowledge | Intent-aware lookup of stored knowledge. Prefers types that match your intent. |
| check_conflicts | The check_conflicts tool exposed by this server. |
| Performance | The Performance tool exposed by this server. |
| cleanup | // Clean specific session cleanup({ scope: "session", session_id: "abc-123" }) |
| start_session | Sessions automatically isolate context—previous events hidden from queries. |
| end_session | The end_session tool exposed by this server. |
| list_sessions | The list_sessions tool exposed by this server. |
| switch_session | The switch_session tool exposed by this server. |
| Configuration | The Configuration tool exposed by this server. |
{
"mcpServers": {
"wormhole": {
"command": "npx",
"args": ["-y", "wormhole"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.