Self-serve · MCP

Your context network,
in supported MCP clients.

DeerDawn MCP briefs Claude Code, Codex, and Cursor on all your projects, decisions, open questions, and working style — so every new session starts caught up, never cold.

One install. One sign-in. Claude Code, Codex, and Cursor each pick up the same brief — every new session starts briefed, never from scratch. If you are looking for AI session memory instead of one more giant reusable prompt, this is the setup path.

Self-serve access is open. Claude Code, Codex, and Cursor use local MCP. Claude.ai connects via remote MCP — no install needed. Just add the server URL and authorize via browser OAuth.

AI context managementhow to share context between AI tools
Prefer remote MCP? Connect in one click →Try the live preview →

Set up in 2 steps

1
Paste prompt 1, restart
Copy the first prompt below and paste it into your AI tool. It writes the config file for you and tells you to restart. One restart is required — MCP servers load at startup.
2
Paste prompt 2, done
After restarting, paste the second prompt. It signs you in, wires up your context file so DeerDawn loads every session, and imports your existing projects. Takes about 30 seconds.

Why this page exists

Most people land here after they realize the real problem is not prompt quality but context continuity. If ChatGPT, Claude, Codex, or Cursor keeps forgetting your project state, the practical fix is session memory — a brief every new session reads — not more copy-paste.

How to make ChatGPT remember context →Claude memory between chats →

Let your AI set it up

Copy this and paste it into Claude, ChatGPT, or any AI tool. It will add the config to the right file for you.

1Paste in Claude Code before restart — sets up the config file
Please set up DeerDawn MCP for me.

Claude Code registers MCP servers through its CLI — it does NOT read a ~/.claude/mcp.json file. Run this command in my terminal:

claude mcp add -s user deerdawn -e DEERDAWN_API_URL=https://api.deerdawn.com -- npx -y @deerdawn/mcp-server@latest

Confirm the command succeeded, then tell me to restart Claude Code. After I restart I'll paste the second prompt.
restart Claude Code, then
2Paste after restart — signs in, configures, imports context
DeerDawn MCP is now loaded. Before installing anything, check whether DeerDawn is already connected — don't assume a fresh setup.

STEP 0 — Check for an existing connection (always do this first):
Call start_session (or deerdawn-start_session if your host prefixes tool names).
- If it returns project or workspace context with no auth error, DeerDawn is ALREADY CONNECTED. Tell me "DeerDawn is already installed and ready" and STOP — skip every step below. Don't request a sign-in URL, and don't call apply_setup or import_local_context. (If those tools don't exist on this host, that's expected — the connected build loads context automatically.)
- If it says I'm not authenticated, continue to step 1.
- If start_session isn't available on this host at all, DeerDawn isn't connected here — continue to step 1.

1. Call get_auth_status (or deerdawn-get_auth_status). If I'm not authenticated, give me the sign-in URL — I'll open it, connect my account, and tell you when done.

2. Call apply_setup (or deerdawn-apply_setup) with surface="claude_code" to update my CLAUDE.md so DeerDawn context loads automatically at the start of every session. (If this tool isn't available, skip it — your connected build already auto-loads context.)

3. Call import_local_context (or deerdawn-import_local_context) with no confirmed flag first to preview any CLAUDE.md, AGENTS.md, or .cursorrules in this repo. (Skip if the tool isn't available.)

4. Then call import_local_context (or deerdawn-import_local_context) with confirmed=true to complete the import.

When you're done, confirm what was set up and tell me DeerDawn is ready.

Or install manually

Choose your tool and paste the config. Node.js 18+ required.

Run in your terminal
claude mcp add -s user deerdawn -e DEERDAWN_API_URL=https://api.deerdawn.com -- npx -y @deerdawn/mcp-server@latest

After pasting, restart your tool. On first use, a browser tab will open to sign in.

What your AI tools can access

list_projects

See all your projects with current task, status, and tech stack at a glance.

get_context

Pull targeted sections — task, decisions, goals, questions — for any project.

update_context

AI tools write back what they learn, keeping your context current across sessions.

cleanup_context

When a task is complete, automatically close it with complete_task=true so open-task command logs are cleared.

get_auth_status

Check authentication status and get a sign-in link if needed.

Related availability

More ways context flows in

Gemini
Remote MCP support for Gemini arrives once Google enables third-party MCP endpoints.
VS Code
MCP support in VS Code Copilot agent mode is tracked — config path will mirror Cursor when available.

Start for free

Create a free account and set up DeerDawn MCP in minutes.