Skip to main content
WalletSuite MCP is in private access. To request an API key and access to the MCP package, contact the WalletSuite team at support@walletsuite.io.
Walks the read and prepare bands — no signing required. For signing, see Choose Your Setup.

​
Prerequisites

  • WalletSuite API key — see Credentials & Authentication
  • An MCP-compatible host or framework - Claude Desktop, Claude Code, LangChain, CrewAI, LlamaIndex or any MCP client
  • Node.js 22+

​
Step 1 — Install (30 seconds)

Add WalletSuite MCP to your client’s MCP config: 
{
  "mcpServers": {
    "walletsuite": {
      "command": "npx",
      "args": ["-y", "@walletsuite/mcp-server"],
      "env": { "WALLETSUITE_API_KEY": "your-key" }
    }
  }
}
The server starts in read mode by default - seven tools for balances, prices, fees, and transaction history. No keys, no signing. Where to put this config depends on your host:
HostConfig Location
Claude Code.mcp.json in your project root
For full framework-specific instructions, see Install Guides.

​
Step 2 — Restart Your Host

After saving the config, restart the application or reload MCP servers from the host settings.

​
Step 3 — Try It

Ask your agent any of these: 
What is the ETH balance of 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045?
You should see a structured response with the balance in ETH and its USD value. Try a few more:
  • What's the price of ETH right now?
  • Show me recent transactions for 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on ethereum
  • Resolve USDC on ethereum — finds the token contract address
  • What would the gas fee be for sending 1 ETH from 0xabc to 0xdef?

​
Step 4 — Expand Access (Optional)

By default, your agent can only read data (MCP_BANDS=read, 7 tools). To allow more: Add transaction preparation when you want the agent to construct payloads: 
"MCP_BANDS": "read,prepare"
This adds 3 tools — prepare_transfer, prepare_serialized_unsigned_tx, prepare_onramp. The agent can now construct unsigned transaction payloads but cannot sign or broadcast them.

​
What Happens Under the Hood

Your agent asks a question
  → MCP host sends a tool call to WalletSuite MCP (running locally)
    → WalletSuite MCP calls the WalletSuite REST API
      → API queries the blockchain
    → WalletSuite MCP returns a structured response
  → Your agent reads the response and answers naturally
No keys are involved for read operations. The MCP server is an orchestration layer that translates natural language into blockchain queries.

​
Production signing

When you’re ready to sign and broadcast, enable the sign and broadcast bands with the full band set: 
"MCP_BANDS": "full"
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 is ever assembled. For headless or multi-agent deployments, issue a scoped agent token bound to a policy (destination allowlists, value caps, rate limits). See Policy Gates for the policy primitives, and Security & Trust for AI Agents for how bands and agent-token scopes bound what the agent can do. If you need the MCP server and the customer-side key share to run on your own infrastructure (HFT, regulated environments), self-host the server over HTTP. Your MPC share never leaves your environment. See Self-Hosting over HTTP. Before enabling signing, read:

​
Next Steps