Skip to main content
Pick your transport (how the MCP server runs). Signing always runs through MPC 2-of-2 (DKLS23): WalletSuite holds one key share, you hold the other, and both are required for every signature.

​
Recommendation table

Your situationTransportWhy
Fastest install, prototype on a single hostnpx over stdioLowest setup overhead; hosted threshold signing, no key infrastructure
Reusable HTTP endpoint for one or more toolsDocker over HTTPURL-based MCP server with no signing infra to operate
Self-hosted MCP server on your own infrastructurestdio or HTTP (your choice)Run the server where you want; your MPC share never leaves your infrastructure
Multi-tenant or platform deploymentHTTPReusable endpoint paired with hosted signing

​
What stdio means

With stdio, your MCP host starts WalletSuite MCP as a local subprocess on the same host. This is the simplest option and the best fit for:
  • Production agent runtimes: LangChain, CrewAI, Pydantic AI, the Claude Agent SDK, and any custom MCP runtime that launches local subprocesses.
  • Development & IDE hosts: Claude Desktop, Claude Code, Cursor, VS Code, Codex, and Windsurf — useful for prototyping and ad-hoc operator workflows.
Use stdio when you want the least operational overhead.

​
What HTTP means

With HTTP, WalletSuite MCP runs as a separate local service and your MCP host connects to it by URL. Choose HTTP when:
  • your client prefers HTTP servers
  • you want one local endpoint that multiple tools can point at
  • you are testing local deployment behavior
For most users, stdio is still simpler.

​
What Docker is for

Docker is the recommended self-hosting path when you want HTTP. It gives you:
  • A repeatable local runtime
  • A clean separation between the client and the MCP server
  • A straightforward path to local HTTP testing
Use Docker if you want an HTTP endpoint without managing a local package runtime yourself. The current documented image is: 
walletsuite/mcp-server:latest
See Self-Hosting Over HTTP for the exact pull and run commands.

​
Signing

Signing runs through MPC 2-of-2 (DKLS23). WalletSuite holds one key share, you hold the other, and both are required for every signature - no full private key ever exists anywhere. See Key Management for the full breakdown. If you want to manage the key yourself in your own code (KMS, HSM, multisig, or a raw key), use the External BYO signing path through the SDK. In that flow MCP can prepare unsigned payloads, but signing happens outside the MCP session.

​
Advanced Configuration: Stateful vs. Stateless HTTP

WalletSuite MCP supports both stateless and stateful HTTP modes, but most users should stay with the default stateless mode.
  • Stateless: Best for simpler request-per-call behavior and lower operational complexity.
  • Stateful: Use this only if you specifically need session-oriented behavior or resumability testing.

​
Best path by audience

​
Production agent runtimes

Use:
  • npx over stdio first
  • HTTP only when the framework prefers a URL-based MCP server
This path fits LangChain, CrewAI, Pydantic AI, the Claude Agent SDK, and custom MCP runtimes that orchestrate tools programmatically in production.

​
Self-hosters

Use:
  • HTTP
  • the walletsuite/mcp-server:latest Docker image first
This path is best when you want a reusable endpoint instead of a host-managed local process.

​
Self-hosted deployments (HFT, regulated)

Use:
  • the self-hosted MCP server over stdio or HTTP
  • the walletsuite/mcp-server:latest Docker image for an HTTP endpoint
Run the MCP server on your own infrastructure when you need full control over where the server lives. Signing still runs through MPC 2-of-2, and your MPC share never leaves your infrastructure. See Self-Hosting Over HTTP.

​
Next steps