DeerDawn MCP Server

Local tools

Claude Code, Cursor, Codex, Claude Desktop, and ChatGPT Desktop all run the MCP server as a local npx -y @deerdawn/mcp-server@latest process. No API key needed in the config: a browser sign-in happens on first use.

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

{
  "mcpServers": {
    "deerdawn": {
      "command": "npx",
      "args": ["-y", "@deerdawn/mcp-server@latest"],
      "env": {
        "DEERDAWN_API_URL": "https://api.deerdawn.com"
      }
    }
  }
}

[mcp_servers.deerdawn]
command = "npx"
args = ["-y", "@deerdawn/mcp-server@latest"]
startup_timeout_sec = 120

[mcp_servers.deerdawn.env]
DEERDAWN_API_URL = "https://api.deerdawn.com"

{
  "mcpServers": {
    "deerdawn": {
      "command": "npx",
      "args": ["-y", "@deerdawn/mcp-server@latest"],
      "env": {
        "DEERDAWN_API_URL": "https://api.deerdawn.com"
      }
    }
  }
}

{
  "mcpServers": {
    "deerdawn": {
      "command": "npx",
      "args": ["-y", "@deerdawn/mcp-server@latest"],
      "env": {
        "DEERDAWN_API_URL": "https://api.deerdawn.com"
      }
    }
  }
}

Web tools: Claude.ai and ChatGPT.com

Claude.ai and ChatGPT.com support remote MCP servers over HTTPS. DeerDawn provides a hosted endpoint, so no local install is needed. Claude.ai authenticates via browser OAuth, the same flow as local tools.

Step 1: Add the remote MCP

Step 2: Ask for DeerDawn when you need it

The hosted server advertises tool descriptions and usage instructions directly to compatible clients. No copied system prompt is required. Ask to “start a DeerDawn session” for orientation, or explicitly ask the client to save a decision, update progress, search context, or manage the task board.

What the MCP server does

Authentication, scopes, and tools

The canonical hosted endpoint is https://api.deerdawn.com/mcp. It uses OAuth 2.1 Authorization Code with PKCE through your browser. Clients discover registration and authorization metadata automatically; you never paste an API key into a web client.

DeerDawn grants the minimum requested scope: context:read for retrieval and context:write for mutations. Access and refresh grants expire within 90 days and refresh tokens rotate. Disconnect DeerDawn in the AI client or revoke the connection in DeerDawn settings to end access immediately.

Limitations and safe use

• The remote server can access only context already stored in your DeerDawn account; it cannot inspect your repository, browse the web, or read an entire AI conversation.
• Tool responses are size-limited and may be truncated. Narrow the query or use pagination when offered.
• AI hosts choose whether to call tools and can misunderstand a request. Verify important context and review all writes.
• DeerDawn rejects unknown fields, oversized inputs, suspicious write content, and unconfirmed destructive actions. Never store secrets or regulated data in project context.

Automatic context cleanup

Completed tasks, resolved questions, and finished goals are automatically removed from your context graph as you work. You don't need to manually clean up. DeerDawn infers completion from what you tell it.

Usage examples

Security & privacy

DeerDawn is designed for professional context: tasks, decisions, and open questions that are often sensitive. Here's what we do to keep that data safe and give you control over it.

Configuration options

Local tools authenticate via browser OAuth, with no API key in the config. Web tools (Claude.ai, ChatGPT.com) also authenticate via browser OAuth, with no API key needed.

Resources