Persistent memory and cross-session learning for AI coding assistants. Cloud-based context management via MCP.
ContextStream MCP server exists for a simple reason — assistants are far more useful when they can act on ContextStream directly instead of describing what you should do. Persistent memory and cross-session learning for AI coding assistants. Cloud-based context management via MCP.
Persistent memory, semantic code search, and team context for Claude Code, Cursor, VS Code Copilot, Windsurf — and every MCP-compatible AI coding assistant.
It works with any MCP client: Claude Code, Cursor, VS Code + GitHub Copilot, Windsurf, Cline, Roo Code, Kilo Code, Codex CLI, OpenCode, Aider, Antigravity, and Claude Desktop.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once ContextStream is connected, these are the calls the assistant has available:
search — semantic, hybrid, keyword, pattern, exhaustive, refactor modesmemory — events, decisions, docs, runbooks, tasks, todos, diagrams, transcriptssession — capture decisions & lessons, recall past sessions, plans, retroactive capturegraph — dependencies, impact analysis, circular deps, unused codecapsule — portable, shareable context snapshots for agent handoffsentity — tickets, incidents, releases, sprints, OKRs, risksskill — reusable instruction + action bundles, portable across toolsmedia — index and search images, video, audio, and documentsYou will need 3 environment variables: CONTEXTSTREAM_API_URL, CONTEXTSTREAM_API_KEY, CONTEXTSTREAM_TOOLSET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. ContextStream's toolset — search, memory, session and 5 more — is a fair guide to whether it matches your workflow. It is maintained by contextstream; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search | semantic, hybrid, keyword, pattern, exhaustive, refactor modes |
| memory | events, decisions, docs, runbooks, tasks, todos, diagrams, transcripts |
| session | capture decisions & lessons, recall past sessions, plans, retroactive capture |
| graph | dependencies, impact analysis, circular deps, unused code |
| capsule | portable, shareable context snapshots for agent handoffs |
| entity | tickets, incidents, releases, sprints, OKRs, risks |
| skill | reusable instruction + action bundles, portable across tools |
| media | index and search images, video, audio, and documents |
{
"mcpServers": {
"contextstream": {
"command": "npx",
"args": ["--prefer-online", "-y", "@contextstream/mcp-server@latest"],
"env": {
"CONTEXTSTREAM_API_URL": "https://api.contextstream.io",
"CONTEXTSTREAM_API_KEY": "your_key",
"CONTEXTSTREAM_TOOLSET": "complete"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CONTEXTSTREAM_API_URL | Endpoint or connection string the server talks to. | Yes |
| CONTEXTSTREAM_API_KEY | Credential the server authenticates with. | Yes |
| CONTEXTSTREAM_TOOLSET | Configuration value read at startup. | Optional |
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.