ContextStream MCP Server

The context platform for AI agents.

Connect your code, docs, and conversations so your agents can find the right files, recall saved decisions, and build on past work across sessions and tools.

The numbers, their sources, and what they do not claim are under Benchmarks.

10,000 monthly credits. No credit card required.

Works with Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI, Qwen Code, Kimi Code, Muse Code, ZCode, Zed, and more MCP clients, on Claude, GPT, Gemini, Kimi, GLM, Qwen, and other models. Create your account or sign in during MCP onboarding. No separate website signup needed.

macOS and Linux

curl -fsSL https://contextstream.io/scripts/mcp.sh | bash

Windows PowerShell

irm https://contextstream.io/scripts/mcp.ps1 | iex

Paste the command into your terminal and follow onboarding to connect your project and supported editor. Restart your editor after setup.

What gets installed and indexed? · Supported clients · Setup guide · Prefer to start on the web?

Ask your connected agent:

Use ContextStream to find the files relevant to my next change. Cite the sources and retrieve any saved project decisions that should guide the work.

Then ask it to save a real decision and its reason. Start a new session and retrieve that decision without explaining it again. Indexing supplies code context; it cannot recover every undocumented decision.

Each benchmark runs through the production API, is registered before its results are read, and is published with its method, confidence interval, and losses.

61 ms median server-side search time (127 ms p95) in the October 27 production run. End to end it was 223 ms, because the client ran in a different region from the one serving the workspace. Your latency depends on your distance from that region.

Competitor figures are as each vendor or the EverMemOS paper published them; we did not re-run them, and readers and judges differ across rows. The code-search baselines come from the August 1 run on the same queries. The agent-task result uses one repository and one agent model, so treat it as directional. Results, methodology, and limitations.

For people ContextStream Create offers one-prompt making to, the server adds one tool, studio: ask for a film, a product explainer filmed from your connected product, an image, sound or music in plain words, and ContextStudio's producer plans the pieces from what your team knows (brand kit, docs, decisions, connected products). There are no models to pick.

• Brand work by name. Brand images (social sets in each network's size, ad sets, hero and product shots, posters and flyers with print PDFs, email headers, brand graphics) and brand sounds (sonic logos, music beds, loops, effect packs, voice-overs, podcast intros and outros): pass form, with sizes (up to 6, such as instagram-post or linkedin-post) or a voice, and the plan keeps to it.
• Plan, then price. plan returns the pieces and one price ("up to N credits, likely about M") and spends nothing. Pass what your agent knows that the workspace may not (the diff it just made, release notes, the doc it has open) as context; the producer reads it next to the team's own context.
• Your go-ahead. make spends at most the plan's price, and only after you agree: a client that can ask you (MCP elicitation, or a stateless input_required result) asks you itself; otherwise the agent passes the price you accepted.
• Following it. status reports each piece while it waits (with notifications/progress where the call asks for them); a product film takes 13 to 21 minutes. result shows images inline and links video and sound (signed links valid about 15 minutes), with each piece's placard. Brand work comes as files, each with its own link: every size as PNG, JPG and WebP with a ZIP of the set, a print PDF, or WAV and MP3 for the web with a broadcast master and stems, plus alt text, a caption and the checks it was held to.
• Revising. revise starts from a made image or sound: a variation (more like it), a revision (it, changed as you say) or a resize (an image in new sizes). Also stop, library, brand and products.
• Email, where Create offers it. Campaigns sent through your team's own Resend account. email_draft writes one in your brand from a prompt ("announce our winter sale to customers") and sends nothing; email_audiences, email_campaigns, email_test (to your own address or Resend's test addresses), email_cancel and email_report (a campaign's delivery, opens, clicks, bounces and complaints, or the workspace's trends). email_send goes only with your go: the client asks you when it can; otherwise the agent shows you the campaign and its recipient count and passes the count you agreed to. email_preview gives a link to share that shows the email in Gmail, Outlook and Apple Mail mockups (desktop, tablet and phone, light and dark, images on or off), with the inbox line and what to check. email_revise changes a draft from plain words ("shorter subject") or sets its subject and preview line; email_duplicate makes a draft copy. email_contacts lists, adds (with where they agreed to hear from you) or unsubscribes contacts; erasing one can't be undone, so it is the delete tool's (studio.email_contact_erase), after your go; email_unsubscribes shows the suppression list with why and when, and takes an address off it only with your go. Resend is connected in the studio, never through an agent: the tool refuses anything shaped like a Resend key.
• Connector. The hosted path /studio serves only this tool, for Claude.ai or ChatGPT connectors, with OAuth tokens bound to that resource (read:studio, write:studio).

Scoped access. Traceable sources. Configurable capture. Indexing sends eligible source contents to ContextStream for hosted search. Transcript saving and local Git metadata capture are on by default and can be turned off. Review data handling and controls before connecting sensitive projects.

npx -y @contextstream/mcp-server@latest setup

https://mcp.contextstream.io/mcp?default_context_mode=fast

contextstream-mcp setup --dry-run
contextstream-mcp doctor
contextstream-mcp doctor --repair

bash -o pipefail -c 'curl -fsSL https://contextstream.io/scripts/mcp.sh | bash'

export CONTEXTSTREAM_API_KEY=...   # or: printf %s "$KEY" | contextstream-mcp configure --api-key-stdin
contextstream-mcp setup --yes --editors=claude --workspace-id=<UUID> --project-path=.

{ "matcher": "Bash", "hooks": [{ "type": "command", "command": "contextstream-mcp hook package-bouncer", "timeout": 8 }] }

{ "version": 1, "hooks": { "beforeShellExecution": [{ "command": "contextstream-mcp hook package-bouncer" }] } }

This repository contains the MIT-licensed Rust MCP server, client, editor setup, and release tooling. The hosted backend is separate and is not included here. See the architecture, release integrity, and latest release.

cargo build --locked -p mcp-server --bin contextstream-mcp
cargo test --locked --workspace

Use the pinned Rust toolchain. For contribution checks and commit sign-off, read CONTRIBUTING.md. Report vulnerabilities using SECURITY.md. See LICENSE, NOTICE, and GOVERNANCE.md for licensing, trademarks, and project governance.

Let humans be human.

Docs · Pricing · Integrations · Benchmarks

Deep project learning starts off for new accounts. Interactive setup offers it once per account (or once when terms change) and remembers if you decline; plain contextstream-mcp setup --yes preserves your current choice.

contextstream-mcp configure --account-learning status   # show current consent state
contextstream-mcp configure --account-learning on       # open privacy page in browser (or print URL)
contextstream-mcp configure --account-learning off      # withdraw consent and queue deletion

--deep-learning is accepted as an alias for --account-learning. Only a person can grant consent by ticking the unchecked box on the signed-in privacy page (https://contextstream.io/dashboard/account/privacy); agents and API keys cannot consent for you. Doctor and init show status only. See data handling and controls.