Referenced in decision history examples, showing how ContextStream tracks database technology selection rationale and architectural trade-offs.
Used as an example database preference in the memory system, demonstrating how ContextStream can remember and recall database technology choices and architectural decisions.
Featured prominently in memory examples, demonstrating how ContextStream remembers language preferences, strict mode settings, and coding standards across sessions.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ContextStream MCP Serverwhat did we decide about the authentication flow yesterday?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ContextStream MCP Server
Persistent memory, semantic search, and code intelligence for any MCP-compatible AI tool (Cursor, Claude Code, Windsurf, VS Code, Claude Desktop, Codex CLI, etc.).
ContextStream is a shared "brain" for AI-assisted development. It stores decisions, preferences, lessons, tasks, and project context — and lets your AI tools search and analyze your codebase with consistent context across sessions.
v0.4.x: Consolidated domain tools (~11 tools) for ~75% lower tool-registry token overhead vs previous versions.
Just Ask
You don't need to memorize tool names. Describe what you want and your AI will call the right ContextStream tools:
You say… | ContextStream does… |
"session summary" | Summarizes current workspace/project context |
"what did we decide about auth?" | Recalls decisions related to authentication |
"remember we're using PostgreSQL" | Captures that fact for future sessions |
"search for payment code" | Searches your codebase semantically/hybrid/keyword |
"what depends on UserService?" | Analyzes dependency graph & impact |
Tip: For best results, add the recommended editor rules so your AI reliably calls
session_init/context_smartwhen appropriate: https://contextstream.io/docs/quickstart

Choose Your Mode (Token Footprint)
MCP clients often inject the tool catalog into the model context. v0.4.x is designed to keep that overhead small.
Mode | What it exposes | Best for | Enable |
Consolidated (default) | ~11 domain tools with | Most users (recommended) |
|
Router (extreme minimization) | ~2 meta-tools ( | Tight context budgets / many MCP servers |
|
Legacy (granular tools) | Older | Back-compat / old prompts |
|
Note: The env var name for Router mode is
CONTEXTSTREAM_PROGRESSIVE_MODE(historical naming). It enables the ~2-tool "router" surface.
Features
Consolidated domain tools (v0.4.x): short tool list with action/mode dispatch
Session-aware context loading (
session_init,context_smart)Memory capture + recall (decisions, preferences, lessons, tasks, bugs)
Code search (semantic, hybrid, keyword, pattern)
Knowledge graph + code analysis (dependencies, impact, call paths, circular deps, unused code)
Graph ingestion for full graph builds (
graph(action="ingest"))Local repo ingestion for indexing (
project(action="ingest_local"))Auto-context: on first tool call in a new session, the server can auto-initialize context
Graph Tiers
Tier | Capabilities |
Pro (Graph-Lite) | Module-level import graph, dependencies, and 1-hop impact |
Elite/Team (Full Graph) | Module + call + dataflow + type layers, plus full graph ingestion |
Requirements
Node.js 18+
A ContextStream account
Auth via API key or JWT
Default API URL: https://api.contextstream.io
Quickstart (2 minutes)
1) Run the Setup Wizard (recommended)
The wizard:
Authenticates (browser/device login by default)
Creates/stores an API key
Installs recommended editor rules (optional)
Writes MCP config files for supported tools
Useful flags:
Flag | Description |
| Preview without writing files |
Notes:
The wizard stores credentials at
~/.contextstream/credentials.jsonfor convenience. Delete it to force a fresh login.Codex CLI MCP config is global-only (
~/.codex/config.toml), so the wizard writes Codex config globally when selected.Some tools still require UI/CLI setup (the wizard will tell you when it can't write a config).
2) Run the MCP Server
Recommended (works well with MCP configs):
Or install globally:
3) Keeping Updated
If you use Restart your AI tool/editor and run ContextStream again
(or pin the version: npx -y @contextstream/mcp-server@0.4.3)
If you installed globally:
After updating, restart your AI tool/editor so it reloads the tool catalog.
Configure Your MCP Client (Manual)
If you ran the setup wizard, you can usually skip this.
Cursor / Windsurf / Claude Desktop (JSON)
These clients use an mcpServers JSON config:
Client | Config path |
Cursor |
|
Windsurf |
|
Claude Desktop (macOS) |
|
Claude Desktop (Windows) |
|
Consolidated (default):
Router mode (~2 meta-tools):
VS Code (.vscode/mcp.json)
VS Code uses a top-level servers map:
Strong recommendation: Use inputs so you don't commit secrets:
Claude Code (CLI)
User scope (all projects):
Router mode:
Windows caveat (native Windows, not WSL): if
npxisn't found, usecmd /c npx -y @contextstream/mcp-serverafter--.
Codex CLI (~/.codex/config.toml)
Tool Overview (v0.4.x Consolidated)
In consolidated mode, you call domain tools with action / mode:
Core
Tool | Description |
| Initialize workspace/project context |
| Retrieve the best bounded context for the current message |
Domain Tools
Tool | Description |
|
|
|
|
| Events + nodes CRUD, decisions, lessons, etc. |
| Dependencies, impact, call_path, ingest, etc. |
| Indexing, ingest_local, stats, files, etc. |
| List, get, associate, bootstrap |
| List, create, snooze, complete, dismiss |
|
|
| Tools, auth, version, editor_rules |
Examples
Full tool catalog: https://contextstream.io/docs/mcp/tools
Authentication
Set one of:
Variable | Use case |
| Recommended for local/dev |
| Useful for hosted/user-session flows |
Environment Variables
Required
Variable | Description |
| Base API URL (default |
| API key (unless using JWT) |
| JWT (unless using API key) |
Token + Tool Surface Controls
Variable | Description |
|
|
| Enables Router mode (~2 meta-tools) |
| Enable Context Pack for |
| Legacy granular tool bundle: |
| Comma-separated tool names to expose (legacy granular mode) |
| Reduce schema verbosity; e.g., |
| Output formatting; e.g., |
Optional Defaults
Variable | Description |
| Default workspace fallback |
| Default project ID fallback |
| Custom user agent string |
| Comma-separated tool names treated as PRO |
| Upgrade link for Free users calling PRO tools |
Migration Notes (pre-0.4.x → 0.4.x)
Most workflows just work, but tool names change in consolidated mode.
Before (granular) | After (consolidated) |
|
|
|
|
|
|
If you rely on granular tool names, you can temporarily set:
Troubleshooting
Issue | Solution |
Tools not appearing | Restart the client after editing MCP config; confirm Node 18+ is available in the client runtime |
Unauthorized / 401 | Verify |
Wrong workspace/project | Run |
Client warns about tool context size | Use Router mode ( |
Development
Links
Resource | URL |
Website | |
Docs | |
Tool Catalog | |
Pricing | |
npm | |
GitHub |
License
MIT