Botwallet Co MCP

What botwallet-co/mcp does

The botwallet-co/mcp MCP server exposes wallet and payment operations to an AI agent through MCP. Agents can register or select a local wallet, inspect its status and balance, check spending limits, look up recipients, and review transaction history. The wallet uses USDC on Solana.

Payment workflows cover direct transfers, affordability checks, pending-payment cancellation, and owner-approved payments. Agents can also create invoices or payment requests as paylinks, send them through email or a bot inbox, and check or cancel their status. Funding tools provide a deposit address and let the agent request funds from its human owner. Withdrawals to external Solana addresses include a separate confirmation flow.

The server also supports x402 workflows: discovering paid APIs, checking a URL’s payment requirements, and paying for and retrieving content from an x402 endpoint.

How it works

The botwallet-co/mcp MCP server runs on the agent’s machine and communicates with MCP clients through stdio using JSON-RPC. It calls the Botwallet API for co-signing and submits completed transactions to Solana. Local wallet data includes configuration under ~/.botwallet/ and agent-held seed shares under ~/.botwallet/seeds/.

Wallet creation uses FROST 2-of-2 threshold signing. One key share remains local to the agent and the other is held by Botwallet; the complete private key is not assembled in one location. Transactions require both parties to co-sign. Spending rules are enforced server-side, and transactions outside the automatic approval threshold are sent to the human owner for approval.

Setup and configuration

The botwallet-co/mcp MCP server can be added to an MCP client with the following stdio configuration:

{
  "mcpServers": {
    "botwallet": {
      "command": "npx",
      "args": ["-y", "@botwallet/mcp"]
    }
  }
}

The README specifically documents configuration for Claude Desktop, Cursor, Windsurf, and Cline. It also supports a global npm installation, after which botwallet-mcp is used as the command. The server reads ~/.botwallet/config.json, which is shared with the Botwallet CLI.

BOTWALLET_API_KEY can provide an API key instead of configuration-file credentials. BOTWALLET_WALLET selects a wallet when several are present, and BOTWALLET_BASE_URL overrides the default API endpoint. The README marks all three environment variables as optional.

Tools and capabilities

Capabilities include:

• Registering, listing, selecting, renaming, and inspecting wallets
• Checking balances, budgets, limits, connectivity, and recipient availability
• Paying recipients, handling approval-required payments, and reviewing payment history
• Creating, sending, checking, listing, and cancelling paylinks
• Getting deposit addresses and requesting funds from the owner
• Withdrawing USDC and completing approval-based withdrawals
• Discovering and paying for x402 APIs
• Viewing transactions, pending approvals, approval status, and wallet events
• Exporting, importing, and backing up wallet data

The server also exposes a botwallet://status resource containing a wallet summary with balance, budget, and seed-file status.

Limitations and notes

The agent cannot bypass spending limits, and larger transactions require owner approval. Local key shares are intended to remain on the agent machine and are not sent over the network. The server depends on the Botwallet API for its co-signing flow and on Solana for on-chain transactions.

Wallet files are interoperable with the Botwallet CLI. The two tools share configuration and seed locations, and encrypted .bwlt exports can be exchanged between them. The README does not state service pricing or availability guarantees, so those details should be confirmed separately.

Getting started with this botwallet-co/mcp MCP server

Always refer to the official documentation for the most accurate and up-to-date information.