Use with any MCP client

The plugin is tuned for Claude Desktop, but primedelta-mcp is a standard MCP server — any MCP-capable client can use it. You self-host the server and point the client at it.

Headless signing

Most non-Claude setups run the server headless (no browser), so use a KMS signer — browser signing is desktop-only. Keep spend caps on. See the signing-modes matrix.

stdio clients (local)

Clients like Cursor, VS Code (MCP), Cline, Windsurf, Zed, and Continue launch a local stdio server. Give them the primedelta-mcp command and its environment. The config shape is the same everywhere — a server entry with a command and env:

{
  "mcpServers": {
    "primedelta": {
      "command": "primedelta-mcp",
      "env": {
        "PRIMEDELTA_MCP_NETWORK": "testnet",
        "PRIMEDELTA_MCP_MODE": "execute",
        "PRIMEDELTA_MCP_KMS_KEY_ID": "<key-id>"
      }
    }
  }
}

Put that wherever the client keeps its MCP config (each client has its own file/UI; the mcpServers block is the portable part). Make sure primedelta-mcp is on the client's PATH.

Where each client keeps its config

These are the typical locations — clients move them between versions, so check your client's current docs if one doesn't match:

Client	Typical config
Claude Code	.mcp.json in the project root
Cursor	.cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
VS Code (Copilot MCP)	.vscode/mcp.json (workspace) — note VS Code uses a top-level servers key rather than mcpServers
Windsurf	~/.codeium/windsurf/mcp_config.json
Cline	its MCP settings file, edited through the extension's UI
Zed	context_servers in settings.json
Continue	mcpServers in ~/.continue/config.json

The shape is the same everywhere: a named server with a command and an env. The one thing to watch is the wrapper key — most use mcpServers, a few (like VS Code) use servers.

Remote clients (HTTP)

For a client that connects to a URL rather than launching a process, run the server over HTTP with authentication and point the client at the https:// endpoint. See Connect Claude web — the same OAuth / bearer setup applies to any remote MCP client.

What you get

Every client sees the same tools — reads, DEX swaps, and whatever gates you enabled. The full list is in the MCP tools reference. The safety model (caps, gates, DID gating) is enforced by the server, so it holds regardless of which client is driving.

What's Claude-specific

The .mcpb one-click install, the config UI, and the built-in prompts (like place a swap safely) are Claude Desktop conveniences. On other clients you wire the config yourself and prompt the model yourself, but the underlying tools and guardrails are identical.