Install Guides

Choose the framework or host where you want to run WalletSuite MCP. All paths require Node.js 22 or newer for the local npx setup.

Claude Desktop
Claude Code
LangChain
CrewAI
Generic MCP Runtime

Claude Desktop reads MCP servers from claude_desktop_config.json.Common locations:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\\Claude\\claude_desktop_config.json

If the file does not exist yet, create it.

Add WalletSuite MCP

{
  "mcpServers": {
    "walletsuite": {
      "command": "npx",
      "args": ["-y", "@walletsuite/mcp-server"],
      "env": {
        "WALLETSUITE_API_KEY": "your-key",
        "MCP_BANDS": "read"
      }
    }
  }
}

After saving, fully restart Claude Desktop so it reloads MCP servers.

Verify

What's the ETH price right now?
Check balances for 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045
Show me recent transactions for 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on ethereum

Troubleshooting

Authentication is required — API key is missing or empty. Check WALLETSUITE_API_KEY.
Server does not appear — verify JSON is valid, file is in the correct location, and Claude Desktop was fully restarted.
npx is not found — install Node.js 22 or newer.

Claude Code supports both local stdio and remote HTTP MCP servers.

stdio via npx (Recommended)

claude mcp add walletsuite --env WALLETSUITE_API_KEY=your-key --env MCP_BANDS=read -- npx -y @walletsuite/mcp-server

Add --scope project (a Claude CLI flag, not a WalletSuite MCP option) to register the server in the project-level .mcp.json so your team shares the same config.On Windows, wrap with cmd /c:

claude mcp add walletsuite --env WALLETSUITE_API_KEY=your-key --env MCP_BANDS=read -- cmd /c npx -y @walletsuite/mcp-server

HTTP endpoint

If you have an HTTP endpoint from Self-Hosting Over HTTP:

claude mcp add --transport http walletsuite http://localhost:3000/mcp

Set WALLETSUITE_API_KEY on the server process, not in the client config.

Verify

claude mcp list

Then try: What's the ETH price right now?

LangChain’s MultiServerMCPClient supports both stdio and http transports.

stdio setup

TypeScript
Python

import { MultiServerMCPClient } from "@langchain/mcp-adapters";

const client = new MultiServerMCPClient({
  walletsuite: {
    transport: "stdio",
    command: "npx",
    args: ["-y", "@walletsuite/mcp-server"],
    env: {
      WALLETSUITE_API_KEY: "your-key",
      MCP_BANDS: "read"
    }
  }
});

from langchain_mcp_adapters.client import MultiServerMCPClient

client = MultiServerMCPClient(
    {
        "walletsuite": {
            "transport": "stdio",
            "command": "npx",
            "args": ["-y", "@walletsuite/mcp-server"],
            "env": {
                "WALLETSUITE_API_KEY": "your-key",
                "MCP_BANDS": "read",
            },
        }
    }
)

HTTP alternative

Start the server with Self-Hosting Over HTTP, then:

TypeScript
Python

const client = new MultiServerMCPClient({
  walletsuite: {
    transport: "http",
    url: "http://localhost:3000/mcp"
  }
});

client = MultiServerMCPClient(
    {
        "walletsuite": {
            "transport": "http",
            "url": "http://localhost:3000/mcp",
        }
    }
)

What to test first

Start with read-only: price lookup, balance checks, asset resolution, transaction history. Add prepare band only when needed.

CrewAI supports MCPServerStdio and MCPServerHTTP in the agent mcps list.

stdio setup

from crewai import Agent
from crewai.mcp import MCPServerStdio

agent = Agent(
    role="Wallet Analyst",
    goal="Use wallet data tools inside a CrewAI workflow",
    backstory="Agent with access to WalletSuite MCP tools",
    mcps=[
        MCPServerStdio(
            command="npx",
            args=["-y", "@walletsuite/mcp-server"],
            env={
                "WALLETSUITE_API_KEY": "your-key",
                "MCP_BANDS": "read",
            },
        )
    ],
)

HTTP alternative

Start the server with Self-Hosting Over HTTP, then:

from crewai import Agent
from crewai.mcp import MCPServerHTTP

agent = Agent(
    role="Wallet Analyst",
    goal="Use a shared WalletSuite MCP endpoint",
    backstory="Agent with access to WalletSuite MCP tools",
    mcps=[
        MCPServerHTTP(
            url="http://localhost:3000/mcp",
            streamable=True,
        )
    ],
)

What to test first

Start with read-only tasks: price lookup, balance checks, asset resolution, transaction history.

Use this when your framework supports MCP but does not have a dedicated guide above.

stdio settings

{
  "command": "npx",
  "args": ["-y", "@walletsuite/mcp-server"],
  "env": {
    "WALLETSUITE_API_KEY": "your-key",
    "MCP_BANDS": "read"
  }
}

HTTP alternative

Start the server with Self-Hosting Over HTTP, then point the runtime at http://localhost:3000/mcp. Set WALLETSUITE_API_KEY on the server process.

Validation

Test with read-only operations first: price lookup, balance checks, transaction history, asset resolution. Expand the band only when needed.

Next steps

Security & Trust — understand the non-custodial model before enabling more capability
OWS Local Signing — enable local signing and broadcast
Tool Reference — full WalletSuite MCP tool surface

Getting Started

Concepts

Advanced

Install Guides

Add WalletSuite MCP

Verify

Troubleshooting

stdio via npx (Recommended)

HTTP endpoint

Verify

stdio setup

HTTP alternative

What to test first

stdio setup

HTTP alternative

What to test first

stdio settings

HTTP alternative

Validation

Next steps

Getting Started

Concepts

Install Guides

Advanced

​Add WalletSuite MCP

​Verify

​Troubleshooting

​stdio via npx (Recommended)

​HTTP endpoint

​Verify

​stdio setup

​HTTP alternative

​What to test first

​stdio setup

​HTTP alternative

​What to test first

​stdio settings

​HTTP alternative

​Validation

​Next steps

Add WalletSuite MCP

Verify

Troubleshooting

stdio via npx (Recommended)

HTTP endpoint

Verify

stdio setup

HTTP alternative

What to test first

stdio setup

HTTP alternative

What to test first

stdio settings

HTTP alternative

Validation

Next steps