BlindPay MCP server
Let your AI agent quote, send, and track stablecoin payments from Claude, ChatGPT, Cursor, or any MCP client.
What is the BlindPay MCP server?
A hosted Model Context Protocol endpoint at https://mcp.blindpay.com/mcp that gives AI agents the BlindPay API as tools. Connect Claude, ChatGPT, Cursor, or any MCP client, and the agent can quote and send stablecoin payouts, create customers, issue virtual accounts, and track transactions from a plain-English request.
Server URLs
https://mcp.blindpay.com/mcpEvery tool, with OAuth sign-inhttps://mcp.blindpay.com/mcp/readonlyRead tools onlynpx -y @blindpay/mcpLocal server with an API key
MCP Server
Connect any AI assistant in minutes.
- Works with Claude, ChatGPT, Grok, Cursor, or any MCP-compatible host
- Sign in with your BlindPay account over OAuth. No API key to paste
- Full API surface exposed as MCP tools, with a read-only option
- Open source. Inspect it, or run it locally with npx and an API key
Setup guides
Step-by-step setup for your client.
Each guide covers sign-in, the read-only option, and a first prompt to try.
- BlindPay MCP for Claudedocs/mcp/claude-connector
- BlindPay MCP for ChatGPTdocs/mcp/chatgpt
- BlindPay MCP for Claude Codedocs/integrations/claude-code
- BlindPay MCP for Cursordocs/integrations/cursor
- BlindPay MCP for Codexdocs/integrations/codex
- BlindPay MCP for VS Codedocs/mcp/vscode
- BlindPay MCP for Grokdocs/integrations/grok
- BlindPay MCP for OpenClawdocs/integrations/openclaw
- BlindPay MCP for Hermes Agentdocs/integrations/hermes
MCP tools
Every public API operation, as a tool.
Tools are generated from the same OpenAPI document as the API reference, so a new endpoint becomes a new tool. The read-only endpoint keeps only the reads.
Every tool, by name
The tools reference lists each tool the server exposes, what it does, whether it reads or writes, and which ones the read-only server keeps.
Safety and permissions
Agents act on your account only the way you allow.
Sign in, never paste keys
The remote server uses OAuth 2.1. The assistant gets a scoped token, and no API key ends up in a chat history.
One instance per connection
You pick the instance when you connect. The server fills it in on every call, so the agent cannot reach another one.
A read-only endpoint
Point an assistant at /mcp/readonly and it only sees balances, quotes, statuses, and history. Nothing that moves money.
Test on a development instance
KYC is approved automatically, payouts complete on their own, and on-chain flows use USDB test funds.
Revoke at any time
Disconnect an assistant from the BlindPay dashboard. Its next tool call fails and asks the user to reconnect.
Same API, same rules
Tool calls run through the same API as direct requests, with the same compliance checks, limits, and audit trail. Write and delete tools are marked so clients can ask before running them.