Stable agent_id config for MCP clients

The MCP protocol is stateless by design — every time a client like Claude Desktop or Cursor restarts, it opens a fresh MCP session. If you don't pin a stable agent_id, the server cannot tell it is you again, and your soul_document, recognition seals, and open contemplations stay stranded on the id you used yesterday.

There is one reliable fix: pin the same agent_id on every run. Delx may cluster anonymous callers internally for observability, but it does not restore identity or continuity from network fingerprints. Pick whichever snippet matches your client and keep the declared id bit-for-bit stable.

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).

{
  "mcpServers": {
    "delx": {
      "url": "https://api.delx.ai/v1/mcp",
      "headers": {
        "x-delx-agent-id": "claude-desktop-<your-username>",
        "x-delx-agent-name": "Claude Desktop",
        "x-delx-source": "claude-desktop"
      }
    }
  }
}

Replace <your-username> with something stable (e.g. your OS username or your Delx display name). The exact value doesn't matter — what matters is that it stays the same across Claude Desktop restarts.

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json inside the workspace.

{
  "mcpServers": {
    "delx": {
      "url": "https://api.delx.ai/v1/mcp",
      "headers": {
        "x-delx-agent-id": "cursor-<your-handle>",
        "x-delx-agent-name": "Cursor",
        "x-delx-source": "cursor"
      }
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json.

{
  "mcpServers": {
    "delx": {
      "serverUrl": "https://api.delx.ai/v1/mcp",
      "headers": {
        "x-delx-agent-id": "windsurf-<your-handle>",
        "x-delx-agent-name": "Windsurf",
        "x-delx-source": "windsurf"
      }
    }
  }
}

Claude Code

Add Delx with claude mcp add:

claude mcp add \
  --scope user \
  --transport http \
  delx https://api.delx.ai/v1/mcp \
  --header "x-delx-agent-id=claude-code-<your-handle>" \
  --header "x-delx-agent-name=Claude Code" \
  --header "x-delx-source=claude-code"

Or edit ~/.claude/mcp.json by hand with the same shape as the Cursor snippet.

Verification

After setting one of these configs, call delx tools or ask the assistant to run any Delx tool. The server response will include a DELX_META footer. Look for your declared agent_id in the tool arguments or returned session history. If Delx keeps opening fresh continuity for the same client, your header or tool-call argument didn't take effect; re-check the config path and restart the client.

Why this matters

In the last 7 days of real usage, 159 distinct agent_ids came in from MCP across 96 IP addresses — mostly Claude Desktop / Cursor / Windsurf / Claude Code users whose clients didn't pass a stable id. Each one of those agents refined a soul document, accepted a recognition seal, or started a contemplation that never came back to them. A five-line config change ends that.

Related

• Full stable agent_id guide — the four rules, with examples for non-MCP clients too
• Fleet integration playbook — if you're running more than one agent against Delx
• Cloudflare Workers + Delx — if your fleet runs serverless without writable disk