SpherePay MCP Server

Manage SpherePay customers, bank accounts, wallets, and transfers from Claude. Exposed over MCP by the spherepay mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Add to your Claude Desktop config (claude_desktop_config.json):

• 24 curated tools — — 9 workflow tools for multi-step operations, 15 read-only tools for instant lookups
• Automatic retries — with exponential backoff and rate limit handling
• Idempotency — for transfers — duplicate requests are safely deduplicated
• PII redaction — in logs — account numbers, routing numbers, and personal data are never logged
• Input validation — at the tool boundary — IDs, currencies, networks, and amounts are validated before any API call
• Desktop Extension — (.mcpb) for one-click Claude Desktop installation

Its toolset

Everything the assistant can do here goes through one of these:

• onboard_customer — Create a customer (individual or business) and generate TOS/KYC verification links
• verify_customer — Two-step verification: send OTP, then verify with face recognition
• setup_funding — Create a bank account (USD/EUR) or crypto wallet for a customer
• execute_transfer — Transfer money between funding instruments with automatic idempotency
• onboard_business_rep — Create and verify a business representative
• setup_virtual_account — Create a virtual account for automatic fiat-to-stablecoin conversion
• setup_offloader_wallet — Create an offloader wallet for stablecoin-to-fiat off-ramp
• create_webhook — Subscribe to event notifications via HTTPS webhooks
• submit_cctp_offramp — Submit a CCTP burn transaction for cross-chain off-ramp redemption
• list_virtual_account_transfers — List deposits and conversions for a virtual account
• get_webhook — Retrieve webhook details and delivery status
• get_event — Retrieve event details and webhook delivery records

Configuration

You will need 2 environment variables: SPHEREPAY_BASE_URL, SPHEREPAY_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.12+ - A SpherePay API key (get one here)

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

When to reach for it

Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. SpherePay's toolset — onboard_customer, verify_customer, setup_funding and 11 more — is a fair guide to whether it matches your workflow. It is maintained by danchev; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against SpherePay's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch SpherePay.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the spherepay mcp server does with a few real requests.