Connect Your Agent

Seashail exposes an MCP server over stdio. Any MCP-capable agent can launch:

seashail mcp

Optional: override network mode for this session:

seashail mcp --network testnet

One-Click Templates

Seashail ships a small set of “one-click” config templates for common clients.

List supported targets:

seashail agent list

Install (workspace-local):

seashail agent install cursor
seashail agent install vscode

Install (global):

seashail agent install windsurf
seashail agent install claude-desktop

Testnet templates (optional):

seashail agent install cursor --network testnet
seashail agent install vscode --network testnet
seashail agent install windsurf --network testnet
seashail agent install claude-desktop --network testnet

These testnet templates run seashail mcp --network testnet, which overrides network mode for that client session only.

Claude Code

Add an MCP server:

claude mcp add seashail seashail mcp

Testnet mode (optional):

claude mcp add seashail-testnet seashail mcp --network testnet

Cursor

Cursor uses .cursor/mcp.json (project) or ~/.cursor/mcp.json (global).

Recommended:

seashail agent install cursor

VS Code / GitHub Copilot

VS Code uses .vscode/mcp.json in a workspace.

Recommended:

seashail agent install vscode

Cline

Cline supports MCP servers via its UI. Configure a server named seashail with:

• Command: seashail
• Args: mcp

Windsurf

Windsurf stores MCP servers in ~/.codeium/windsurf/mcp_config.json.

Recommended:

seashail agent install windsurf

OpenClaw

If your OpenClaw build supports MCP stdio servers directly, configure a server named seashail that runs:

seashail mcp

If your OpenClaw build does not support MCP natively, use an MCP bridge/proxy that can launch a local stdio MCP server and forward tool calls to it.

Codex

Configure an MCP stdio server named seashail that runs:

seashail mcp

Testnet mode (optional):

seashail mcp --network testnet

Config Snippets

You can copy templates from:

• packages/agent-configs/templates/cursor/mcp.json
• packages/agent-configs/templates/cursor/mcp.testnet.json
• packages/agent-configs/templates/vscode/mcp.json
• packages/agent-configs/templates/vscode/mcp.testnet.json
• packages/agent-configs/templates/windsurf/mcp_config.json
• packages/agent-configs/templates/windsurf/mcp_config.testnet.json
• packages/agent-configs/templates/claude-desktop/claude_desktop_config.json
• packages/agent-configs/templates/claude-desktop/claude_desktop_config.testnet.json

Multi-Client Behavior

MCP is stdio-based, so each agent will launch a seashail mcp process.

Seashail avoids split-brain keys/state by using a singleton local daemon:

• seashail mcp runs as a thin stdio proxy
• it forwards all requests to seashail daemon, which owns the keystore and passphrase session
• if no daemon is running, seashail mcp will autostart it

This means multiple agents can safely share:

• the same wallets and keystore
• the same in-memory passphrase session
• the same policy counters (daily caps, etc.)

Local transport is IPC-only:

• macOS/Linux: Unix socket at data_dir/seashail-mcp.sock
• Windows: named pipe (no TCP listener)

Debugging only: seashail mcp --standalone runs a direct stdio server without sharing state across clients.