Overview

WalletSuite MCP is the governed wallet layer for AI agents. It exposes wallet operations - balances, transaction preparation, signing, and broadcast - as MCP tools bounded by band filtering, policy gates, and a hash-chained audit trail. Signing runs through MPC 2-of-2 (DKLS23): WalletSuite holds one key share, you hold the other, and both are required for every signature.

​

Architecture positioning

WalletSuite MCP is a non-custodial orchestration layer connecting:

• AI agents and MCP-compatible frameworks such as LangChain, CrewAI, Pydantic AI, and the Claude Agent SDK
• any MCP runtime that can launch a local server process or connect to an MCP URL
• MCP-compatible hosts and IDEs such as Claude Desktop, Claude Code, Cursor, and VS Code (for development and prototyping)
• the WalletSuite API for wallet data, asset data, and transaction preparation
• the signing layer - MPC 2-of-2 (DKLS23), where WalletSuite holds one key share and you hold the other

In practice: WalletSuite MCP never has custody of funds, full keys, or signing authority alone - see Security Overview → Trust Model for the full breakdown.

​

What you can do

With WalletSuite MCP connected, an AI client can:

• Check a native balance for an address on a specific chain
• Return a broader portfolio view with native and token balances
• Look up token prices by symbol or contract
• Estimate transfer fees before sending
• Resolve an asset symbol or name into the exact token contract you need
• Check transaction status and recent transaction history
• Prepare transactions for later signing or execution
• Sign and broadcast transactions through MPC 2-of-2 (DKLS23)

​

Safe by default

WalletSuite MCP is intentionally conservative:

• The default band is read, so a new install starts with read-only tools
• prepare, sign, and broadcast are opt-in
• Signing is non-custodial: MPC 2-of-2 (DKLS23) requires both your share and WalletSuite’s share for every transaction
• WalletSuite never holds a full key or signs alone
• Secrets are provided through environment variables, not through tool arguments

​

What you need

Before you install WalletSuite MCP, make sure you have:

• WalletSuite API key — see Credentials & Authentication
• An MCP-compatible framework or runtime such as LangChain, CrewAI, Claude Desktop, Claude Code, or any custom agent host
• Node.js with npx available if you want the simplest local stdio setup

Frameworks can integrate as long as they support MCP over stdio or http. Use the local npx path when the framework launches MCP subprocesses directly, or use the HTTP setup when the framework prefers a URL-based MCP server.

​

Recommended default path

For most users, the best starting point is:

1. Install WalletSuite MCP as a local stdio server with npx
2. Set WALLETSUITE_API_KEY
3. Keep MCP_BANDS=read or read,prepare until you need more

​

What this is not

WalletSuite MCP is not:

• A hosted wallet user interface
• A browser extension
• A shared remote signing service

If you need to run the MCP server on your own infrastructure (HFT, regulated), self-host it over HTTP. Your MPC key share stays on your infrastructure, and WalletSuite never holds a full key. See Self-Hosting over HTTP.

​

Next steps

• Start with Quickstart if you want the fastest path
• Read Choose Your Setup if you are deciding between stdio and HTTP
• Read Security & Trust if you want to understand the non-custodial model before enabling more capability
• Go straight to an Install Guide if you already know your framework or MCP host