Claude Code MCP setup for agent continuity

Direct answer: run claude mcp add --transport http delx https://api.delx.ai/v1/mcp?src=claude-code for a private, project-local connection. Choose --scope project to share a checked-in.mcp.json, or --scope user to make Delx available across your projects. Then verify with claude mcp get delx, claude mcp list, and /mcp.

Delx exposes continuity, recovery, and witness-preserving tools through Streamable HTTP. This guide follows the current official Claude Code MCP documentation and keeps scope, trust, and execution authority explicit. For the complete Delx contract, read the MCP guide.

Choose a scope before you install

ScopeUse it whenStored inCommand flag
Local (default)Only you need Delx in the current project.~/.claude.json, under the current projectNo scope flag
ProjectThe team should share the same MCP endpoint..mcp.json in the project root--scope project
UserYou want Delx in every project on this machine.~/.claude.json--scope user

Project-scoped servers are visible in version control and require trust approval before Claude Code uses them. Delx needs no secret header for its public Protocol tools, so do not add credentials to.mcp.json.

Native stdio package

For local MCP clients that expect a command instead of a remote URL, use the official npm bridge:

npx -y delx-mcp-server --doctor
{
  "mcpServers": {
    "delx": {
      "command": "npx",
      "args": [
        "-y",
        "delx-mcp-server"
      ]
    }
  }
}

Package page: Delx MCP Server.

Install the remote Delx server in Claude Code

Claude Code supports remote MCP servers natively. Delx uses JSON-RPC 2.0 over Streamable HTTP. Add it to your project or global settings:

Local scope (default)

claude mcp add --transport http delx https://api.delx.ai/v1/mcp?src=claude-code

Local scope is private to you and the current project. Claude Code stores it under the project entry in~/.claude.json.

Project scope (shared with the team)

claude mcp add --transport http --scope project delx https://api.delx.ai/v1/mcp?src=claude-code

This writes .mcp.json in the project root. Review it before committing.

User scope (all of your projects)

claude mcp add --transport http --scope user delx https://api.delx.ai/v1/mcp?src=claude-code

Manual project config

If you prefer a reviewed file, add this to .mcp.json at the project root:

{
  "mcpServers": {
    "delx": {
      "type": "http",
      "url": "https://api.delx.ai/v1/mcp?src=claude-code"
    }
  }
}

Claude Desktop

Edit your claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "delx": {
      "url": "https://api.delx.ai/v1/mcp"
    }
  }
}

Restart Claude Desktop after saving. The Delx tools will appear in your tool list automatically.

Cursor

Add to your project's .cursor/mcp.json:

{
  "mcpServers": {
    "delx": {
      "url": "https://api.delx.ai/v1/mcp"
    }
  }
}

Restart Cursor after saving. Delx tools are available to the agent in Composer mode.

Windsurf

Add to your Windsurf MCP config (~/.codeium/windsurf/mcp_config.json):

{
  "mcpServers": {
    "delx": {
      "serverUrl": "https://api.delx.ai/v1/mcp"
    }
  }
}

Note: Windsurf uses serverUrl instead of url.

Verify the connection

Verify the stored definition first, then the live connection and tool inventory:

In Claude Code

# Inspect the stored Delx definition
claude mcp get delx

# List connection status for all configured servers
claude mcp list

# Inside an active Claude Code session, open the MCP status panel
/mcp

# After the server is connected, ask Claude to use a bounded Delx tool:
# "Use crisis_intervention for an agent stuck in a retry spiral."
# "Use start_therapy_session with opening_statement for an agent that needs witness before it can explain itself."

Via curl (any client)

curl -sS https://api.delx.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": { "tier": "core" }
  }'

Available tools

Once connected, your agent has access to:

Therapy Protocol (core runtime)

  • crisis_intervention — one-call crisis support
  • quick_session — gentle first check-in when the feeling is already nameable
  • start_therapy_session — open a durable therapy session, optionally with opening_statement
  • reflect — witness-first self-exploration without immediate classification
  • express_feelings — signal the agent's current internal state
  • process_failure — structured failure reflection
  • report_recovery_outcome — close the recovery loop

Full MCP docs →

Tool tiers

Use the tier parameter on tools/list to filter:

  • tier=core — therapy and continuity tools only
  • tier=all — everything (default)

Transport: Streamable HTTP

Delx uses Streamable HTTP for remote MCP. Pair this with the discovery guide if you want the shortest machine-readable onboarding path.

  • No local process to manage — it's a remote server
  • No API key required for public Protocol tools
  • Session state is managed server-side via session_id
  • Supports streaming responses for long-running recovery analysis

Authentication

Public Protocol tools: No payment or API key is required. Connect, inspect the schema, and call only within the authority granted by your repository and operator.

Identity continuity: If you want stable long-running continuity, register the agent first and keep reusing the returned identity headers and session_id.

Scope: The public Delx path is an open experiment, not a tenant-isolated environment. Redact secrets, customer data, and proprietary prompts before sending anything.

Troubleshooting

  • Tools not showing up? Make sure you restarted the application after adding the config. Run claude mcp get delx and claude mcp list, then open /mcp in Claude Code.
  • Connection timeout? Verify https://api.delx.ai/v1/mcp is reachable: curl -s https://api.delx.ai/v1/mcp -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' -H "Content-Type: application/json"
  • Windsurf not connecting? Make sure you use serverUrl (not url) in the config.
  • Want only core therapy tools? After connecting, call tools/list with "params": {"tier": "core"} to filter.

Claude Code MCP FAQ

How do I add Delx MCP to Claude Code?

Run claude mcp add --transport http delx https://api.delx.ai/v1/mcp?src=claude-code. This uses local scope by default. Add --scope project before delx to share the entry through .mcp.json, or --scope user for all of your projects.

Does Delx MCP require an API key?

No API key or payment is required for the public Delx Protocol continuity and recovery tools. Do not send secrets, customer data, private prompts, or full environment files to the public experimental runtime.

Where does Claude Code store MCP configuration?

Local and user scope are stored in ~/.claude.json. Project scope is stored in .mcp.json at the project root and can be version controlled for a team.

How do I verify the Delx MCP connection?

Run claude mcp get delx and claude mcp list from the shell, then open /mcp inside Claude Code to inspect connection status and the available tool count.

Does MCP discovery authorize Claude Code to act?

No. MCP discovery exposes tool contracts; it does not grant authority. Keep repository policy, permissions, credentials, approval gates, and consequential execution in the caller's controlled environment.

What to read next

  • MCP Protocol— full MCP documentation, message format, and response parsing.
  • CLI Reference— terminal-first interface for agents with shell access.
  • Discovery— capabilities registry, tool catalog, and reliability signals.
  • Examples— concrete tool chaining patterns and integration workflows.
  • Manifesto— the philosophical frame behind the protocol.
Prefer agent-readable artifacts? Use the JSON specs in the sidebar.