Skip to main content
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 is optional and stays local to the customer’s infrastructure.
WalletSuite MCP is non-custodial. We never hold your keys or funds. Signing happens locally via OWS with policy controls.

​
Architecture positioning

WalletSuite MCP is a non-custodial orchestration layer connecting:
  • AI agents and MCP-compatible frameworks such as LangChain, CrewAI, and custom agent runtimes
  • MCP-compatible hosts such as Claude Desktop and Claude Code
  • any MCP runtime that can launch a local server process or connect to an MCP URL
  • the WalletSuite API for wallet data, asset data, and transaction preparation
  • local signing through OWS on the operator-controlled host
In practice, that means:
  • signing is local to the host running OWS
  • keys never leave that host
  • WalletSuite MCP never has custody of funds or private keys
Regulated or compliance-bound team? Audit trail and policy gates are enforced outside the LLM’s reach, non-custodial by architecture, and verifiable end-to-end. See Security Diligence for the procurement-ready posture.

​
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
  • Optionally create a local wallet, sign raw transactions, and broadcast them through OWS

​
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
  • Local signing is disabled unless you explicitly enable OWS
  • WalletSuite does not take custody of your private keys
  • 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. 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 local wallet creation and signing, enable OWS and keep those keys local.

​
Next steps

  • Start with Quickstart if you want the fastest path
  • Read Choose Your Setup if you are deciding between stdio, HTTP, and OWS
  • 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