Skip to main content
Most users should start with a local stdio server installed through npx. It is the fastest path, requires the least setup, and keeps the MCP server colocated with the host process.

​
Recommendation table

Your situationRecommended setupWhy
You want the fastest installnpx over stdioLowest setup overhead and best default path
You need a reusable HTTP endpointDocker image over HTTPBest when your client or workflow prefers a URL-based MCP server
You need local signing and local broadcastEnable OWSAdds wallet creation, signing, and send tools that run through the local OWS vault — keys stay on the operator host

​
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:
  • Agent Frameworks: LangChain, CrewAI, and generic MCP runtimes that launch local subprocesses.
  • Desktop & IDE Hosts: Claude Desktop, Claude Code, Cursor, VS Code, Codex, and Windsurf.
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.

​
What OWS is for

OWS (Open Wallet Standard) adds optional local signing and broadcast capabilities. Leave it off unless you need:
  • Local wallet creation
  • Detached signing of raw unsigned transaction hex
  • Local sign-and-send through a configured RPC URL

​
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

​
Agent frameworks and runtimes

Use:
  • npx over stdio first
  • HTTP only when the framework prefers a URL-based MCP server
This path fits LangChain, CrewAI, and other MCP runtimes that orchestrate tools programmatically.

​
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.

​
Advanced local signers

Use:
  • OWS
  • owner mode first
Add broadcast only after you have confirmed the local signing flow and RPC configuration.

​
Next steps