Create project
Connect your agent

acme-web

Created just now

proj_8f3k2 · created 11:29 AM

Persistent memory for this project — decisions, docs, and lessons your agent can query. Less lost context.

Listening for your agent…

Paste the config for your client below — that's the whole setup. 0:00

Connected — Claude Code · 11:32 AM

First call verified. acme-web now answers your agent with everything it knows.

No successful call yet.

We listened for 2:00. Here's what the server actually saw — and the exact fix.

Demo state

.mcp.json· project root

{
  "mcpServers": {
    "contextstream": {
      "type": "http",
      "url": "https://mcp.contextstream.io/mcp",
      "headers": {
        "Authorization": "Bearer csk_live_…"
      }
    }
  }
}

Save, then restart Claude Code in this repo — it picks up .mcp.json automatically. Replace csk_live_… with your project key from .

.cursor/mcp.json· project root

{
  "mcpServers": {
    "contextstream": {
      "url": "https://mcp.contextstream.io/mcp",
      "headers": {
        "Authorization": "Bearer csk_live_…"
      }
    }
  }
}

Save, then enable it under Cursor Settings → MCP. Replace csk_live_… with your project key from .

~/.codex/config.toml· home directory

# add to ~/.codex/config.toml
[mcp_servers.contextstream]
url = "https://mcp.contextstream.io/mcp"
bearer_token = "csk_live_…"

Save, then restart codex. Replace csk_live_… with your project key from .

This flips green the moment your agent makes its first call.

First tool called groundingClaude Code · 11:32 AM First context returned acme-web — Next.js 14 storefront. Decisions: App Router, Prisma + Postgres. 3 context items seeded from project setup…

What we saw 3 auth failures · last 11:31:02

What it means

Your API key was rejected — the key in your config doesn't match any active key for acme-web.

Exact fix

What we saw 0 requests received in 2:00

What it means

Your agent never loaded the config — usually the file isn't where the client looks, or the client wasn't restarted after you added it.

Exact fix

What we saw 14 calls · project acme-api · last 11:33:41

What it means

The key in your config belongs to acme-api, not acme-web. Your agent is connected — just to the wrong project.

Exact fix

Demo

Timeout check runs at 2:00 with no successful call.

Server fixture

Context items

Nothing here yetDecisions, docs, and lessons appear as your agent works.

Project brief — goals, stack, conventionsdoc

Use Next.js App Router + server componentsdecision

TypeScript strict mode; no default exportspreference

Recent activity

—1

No calls yetActivity shows up after your agent's first call.

grounding · Claude Code · 11:32 AMreturned 3 items