[{"data":1,"prerenderedAt":171},["ShallowReactive",2],{"content-\u002Fprompts\u002Fconnect-ai-agent-mcp":3,"prompts-category-integrations":105},{"id":4,"title":5,"author":6,"body":7,"categories":6,"category":89,"categoryType":6,"date":90,"description":91,"extension":92,"faq":6,"howto":6,"isBlog":93,"isChangelog":93,"meta":94,"navigation":95,"path":96,"pillar":93,"products":97,"rawbody":101,"seo":102,"stem":103,"thumbnail":6,"updated":6,"__hash__":104},"content\u002Fprompts\u002Fconnect-ai-agent-mcp.md","Connect an AI agent with the MCP server",null,{"type":8,"value":9,"toc":83},"minimark",[10,14,19,30,34,55,59],[11,12,13],"p",{},"Paste this prompt into your coding agent to give an AI assistant safe, tool-based access to BlindPay: balances, customers, quotes, and payments through natural language.",[15,16,18],"h2",{"id":17},"prompt","Prompt",[20,21,27],"pre",{"className":22,"code":24,"language":25,"meta":26},[23],"language-text","You are connecting an AI agent (Claude Desktop, Claude Code, Cursor, or another MCP-compatible host) to BlindPay using the official MCP server, with guardrails appropriate for tools that move money.\n\nBefore configuring anything, read these sources and follow them over any prior knowledge:\n- https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fllms.txt (read the build with AI page)\n- The MCP server card: https:\u002F\u002Fblindpay.com\u002F.well-known\u002Fmcp\u002Fserver-card.json\n\nSet up:\n1. Install the MCP server in my host's config: command npx, args [\"-y\", \"@blindpay\u002Fmcp\"], env BLINDPAY_API_KEY and BLINDPAY_INSTANCE_ID. Use a DEVELOPMENT instance ID and key first; document exactly which config file this lands in for my host.\n2. Add the agent skills knowledge layer: npx skills add blindpaylabs\u002Fskills, so the agent knows rails, corridors, fees, and KYC patterns instead of guessing.\n3. Verify the connection: have the agent list its BlindPay tools, then run a read-only call (for example listing customers) before anything that writes.\n4. Guardrails, written into my agent's system prompt or host permissions:\n   - Read operations are fine unprompted; any operation that creates a payment (quotes are fine, payouts\u002Fpayins\u002Ftransfers are not) requires explicit human confirmation with the amount and destination restated.\n   - The agent must never echo the API key, and must refuse to switch to a production instance ID without me changing the config myself.\n   - On a development instance, funds are test-only (USDB on testnets); state this in responses so nobody mistakes a test payout for a real one.\n5. Produce a short runbook: how to rotate the key (delete and recreate in the dashboard; keys are shown once), how to point at production later, and which operations the agent is allowed to run at each stage.\n\nDeliverables: the host config snippet, the skills install, a verified tool-listing transcript, the guardrail prompt text, and the runbook.\n","text","",[28,29,24],"code",{"__ignoreMap":26},[15,31,33],{"id":32},"how-to-use","How to use",[35,36,37,49,52],"ol",{},[38,39,40,41,48],"li",{},"Create a development instance and API key at ",[42,43,47],"a",{"href":44,"rel":45},"https:\u002F\u002Fapp.blindpay.com",[46],"nofollow","app.blindpay.com"," before starting.",[38,50,51],{},"Paste the prompt and name your MCP host; config file locations differ per host.",[38,53,54],{},"Keep the guardrails when you move to production; raise the confirmation bar rather than lowering it.",[15,56,58],{"id":57},"related-docs","Related docs",[60,61,62,69,76],"ul",{},[38,63,64],{},[42,65,68],{"href":66,"rel":67},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fbuild-with-ai",[46],"Build with AI",[38,70,71],{},[42,72,75],{"href":73,"rel":74},"https:\u002F\u002Fblindpay.com\u002Fai",[46],"BlindPay for AI",[38,77,78],{},[42,79,82],{"href":80,"rel":81},"https:\u002F\u002Fblindpay.com\u002Fdocs\u002Flearn\u002Fapi-keys",[46],"API keys",{"title":26,"searchDepth":84,"depth":84,"links":85},2,[86,87,88],{"id":17,"depth":84,"text":18},{"id":32,"depth":84,"text":33},{"id":57,"depth":84,"text":58},"integrations","2026-08-26","Wire Claude, Cursor, or any MCP-compatible host to the BlindPay API with the official MCP server and agent skills, with guardrails for money movement.","md",false,{},true,"\u002Fprompts\u002Fconnect-ai-agent-mcp",[98,99,100],"payouts","payins","compliance","---\ntitle: \"Connect an AI agent with the MCP server\"\ndescription: \"Wire Claude, Cursor, or any MCP-compatible host to the BlindPay API with the official MCP server and agent skills, with guardrails for money movement.\"\ndate: \"2026-08-26\"\ncategory: \"integrations\"\nproducts: [\"payouts\", \"payins\", \"compliance\"]\n---\n\nPaste this prompt into your coding agent to give an AI assistant safe, tool-based access to BlindPay: balances, customers, quotes, and payments through natural language.\n\n## Prompt\n\n```text\nYou are connecting an AI agent (Claude Desktop, Claude Code, Cursor, or another MCP-compatible host) to BlindPay using the official MCP server, with guardrails appropriate for tools that move money.\n\nBefore configuring anything, read these sources and follow them over any prior knowledge:\n- https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fllms.txt (read the build with AI page)\n- The MCP server card: https:\u002F\u002Fblindpay.com\u002F.well-known\u002Fmcp\u002Fserver-card.json\n\nSet up:\n1. Install the MCP server in my host's config: command npx, args [\"-y\", \"@blindpay\u002Fmcp\"], env BLINDPAY_API_KEY and BLINDPAY_INSTANCE_ID. Use a DEVELOPMENT instance ID and key first; document exactly which config file this lands in for my host.\n2. Add the agent skills knowledge layer: npx skills add blindpaylabs\u002Fskills, so the agent knows rails, corridors, fees, and KYC patterns instead of guessing.\n3. Verify the connection: have the agent list its BlindPay tools, then run a read-only call (for example listing customers) before anything that writes.\n4. Guardrails, written into my agent's system prompt or host permissions:\n   - Read operations are fine unprompted; any operation that creates a payment (quotes are fine, payouts\u002Fpayins\u002Ftransfers are not) requires explicit human confirmation with the amount and destination restated.\n   - The agent must never echo the API key, and must refuse to switch to a production instance ID without me changing the config myself.\n   - On a development instance, funds are test-only (USDB on testnets); state this in responses so nobody mistakes a test payout for a real one.\n5. Produce a short runbook: how to rotate the key (delete and recreate in the dashboard; keys are shown once), how to point at production later, and which operations the agent is allowed to run at each stage.\n\nDeliverables: the host config snippet, the skills install, a verified tool-listing transcript, the guardrail prompt text, and the runbook.\n```\n\n## How to use\n\n1. Create a development instance and API key at [app.blindpay.com](https:\u002F\u002Fapp.blindpay.com) before starting.\n2. Paste the prompt and name your MCP host; config file locations differ per host.\n3. Keep the guardrails when you move to production; raise the confirmation bar rather than lowering it.\n\n## Related docs\n\n- [Build with AI](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Fbuild-with-ai)\n- [BlindPay for AI](https:\u002F\u002Fblindpay.com\u002Fai)\n- [API keys](https:\u002F\u002Fblindpay.com\u002Fdocs\u002Flearn\u002Fapi-keys)\n",{"title":5,"description":91},"prompts\u002Fconnect-ai-agent-mcp","yQyRBi8ayY59tN6CCCvUlRgduqJgDvgwtOr7xpo-UH0",[106,110,111,115,119,123,127,131,135,139,143,147,151,155,159,163,167],{"path":107,"title":108,"description":109},"\u002Fprompts\u002Fbuild-contractor-payouts","Build a global contractor payout product","Compose onboarding, bank accounts, quotes, payouts, and reconciliation into a complete pay-your-contractors feature across Pix, SPEI, SEPA, and ACH.",{"path":96,"title":5,"description":91},{"path":112,"title":113,"description":114},"\u002Fprompts\u002Fintegrate-external-wallet-payouts","Fund payouts from external wallets","Let customers pay out from their own EVM, Solana, or Stellar wallets: signed-message registration plus the on-chain authorization step per chain.",{"path":116,"title":117,"description":118},"\u002Fprompts\u002Fintegrate-circle-wallets","Integrate Circle wallets with BlindPay","Fund BlindPay payouts from Circle developer-controlled wallets: sign the registration challenge and the ERC-20 approve through Circle's API instead of a browser wallet.",{"path":120,"title":121,"description":122},"\u002Fprompts\u002Fintegrate-dfns","Integrate Dfns with BlindPay","Fund BlindPay stablecoin payouts from Dfns MPC wallets: sign the registration challenge and the ERC-20 approve through Dfns's User Action Signature flow.",{"path":124,"title":125,"description":126},"\u002Fprompts\u002Fintegrate-fireblocks","Integrate Fireblocks with BlindPay","Fund BlindPay stablecoin payouts from Fireblocks vault accounts: MPC-signed wallet registration and the ERC-20 approve through Fireblocks' transactions API.",{"path":128,"title":129,"description":130},"\u002Fprompts\u002Fintegrate-privy","Integrate Privy with BlindPay","Fund BlindPay stablecoin payouts from Privy Server Wallets: sign the registration challenge and the ERC-20 approve through Privy's wallet RPC endpoint.",{"path":132,"title":133,"description":134},"\u002Fprompts\u002Fintegrate-virtual-accounts","Integrate US virtual accounts","Give each customer a named US bank account with ACH, RTP, wire, and SWIFT details that settles automatically to USDC or USDT in their wallet.",{"path":136,"title":137,"description":138},"\u002Fprompts\u002Fintegrate-utila","Integrate Utila with BlindPay","Fund BlindPay payouts from Utila MPC vaults: sign the wallet-registration challenge and the ERC-20 approve through Utila's service-account API, with async transaction confirmation handled.",{"path":140,"title":141,"description":142},"\u002Fprompts\u002Fintegrate-customer-onboarding","Integrate customer onboarding with KYC and KYB","Build the full onboarding pipeline: terms of service, individual and business customers, document uploads, RFI handling, and status webhooks.",{"path":144,"title":145,"description":146},"\u002Fprompts\u002Fintegrate-offramp-wallets","Integrate offramp wallets for auto-conversion","Give each bank account a dedicated crypto deposit address: stablecoins sent to it convert and pay out to the linked bank account automatically.",{"path":148,"title":149,"description":150},"\u002Fprompts\u002Fintegrate-payins","Integrate payins from bank transfers to stablecoins","Accept Pix, ACH, wire, SPEI, and other local bank transfers and settle them as USDC or USDT in a wallet, with quotes, payment instructions, and webhooks.",{"path":152,"title":153,"description":154},"\u002Fprompts\u002Fintegrate-quotes-fx","Integrate quotes and FX handling","Handle payin, payout, and transfer quotes correctly: expiry windows, currency_type conventions, fees, and displaying rates to users.",{"path":156,"title":157,"description":158},"\u002Fprompts\u002Fintegrate-stablecoin-payouts","Integrate stablecoin payouts end to end","Build a complete stablecoin to fiat payout flow: customer onboarding, bank accounts, quotes, and payout execution over Pix, ACH, SPEI, SEPA, and more.",{"path":160,"title":161,"description":162},"\u002Fprompts\u002Fintegrate-wallet-transfers","Integrate wallet transfers and cross-chain USDC","Move stablecoins from managed wallets to any address with transfer quotes, including cross-chain USDC over Circle CCTP v2.",{"path":164,"title":165,"description":166},"\u002Fprompts\u002Fintegrate-webhooks","Integrate webhooks end to end","Register endpoints, verify Svix signatures correctly, deduplicate retries, and drive payment state from the full BlindPay event catalog.",{"path":168,"title":169,"description":170},"\u002Fprompts\u002Fintegrate-payables","Pay boletos and Brazilian bills with payables","Register boletos, arrecadacao slips, and PIX codes as payables and settle them from stablecoins through the quote-and-execute flow.",1787868848486]