Delivers payment approval requests via Telegram so the user can approve or reject pending one-time card and recharge requests before any charge occurs.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@TunaPay MCP Buy me one month of Cursor Pro."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Let your AI assistant pay online with a TunaPay prepaid USD Visa card, while you stay in control of every cent.
Works with Claude (desktop and web), Claude Code, Cursor, and any client that speaks the Model Context Protocol.
You approve every payment. The AI can only create a pending request. Nothing is charged until you tap approve in Telegram or on tunapay.ai. Requests expire after 10 minutes.
One card per purchase. Each approved request opens a one-time card loaded with exactly the amount needed. It freezes itself after that one payment.
Your wallet, your cards. Money only moves from your own TunaPay wallet onto your own card. The plugin cannot send crypto or pay another person.
Your key, revocable anytime. You create a personal plugin key on the tunapay.ai member page and can revoke it with one click.
Related MCP server: payclaw-mcp
Sign up at tunapay.ai and top up your wallet.
Open the member page, go to AI payment plugin, and create a plugin key (it starts with tpk_).
The plugin is available to TunaPay membership-tier members.
Settings → Connectors → Add custom connector, paste:
https://tunapay.ai/gw/mcpClaude opens the TunaPay approval page; sign in and click Allow.
claude mcp add --transport http tunapay https://tunapay.ai/gw/p/mcp --header "Authorization: Bearer tpk_YOUR_KEY"Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"tunapay": {
"url": "https://tunapay.ai/gw/p/mcp",
"headers": { "Authorization": "Bearer tpk_YOUR_KEY" }
}
}
}This repository is a zero-dependency local server (Node.js 18+) that talks to the same TunaPay API. Use it with any client that launches local MCP servers:
{
"mcpServers": {
"tunapay": {
"command": "npx",
"args": ["-y", "github:tunakingrwa/tunapay-mcp"],
"env": { "TUNAPAY_KEY": "tpk_YOUR_KEY" }
}
}
}Tool | What it does | Moves money? |
| Wallet balance and how approvals reach you | No |
| Which card has actually been charged successfully at a given merchant | No |
| Your cards (last 4 digits, status, balance), never full numbers | No |
| Ask you to approve a one-time card for one purchase | Only after you approve |
| Ask you to approve topping up one of your cards | Only after you approve |
| Status of a request (pending, done, expired…) | No |
| Card details of an unused one-time card this plugin opened, to fill a checkout | No |
"Buy me one month of Cursor Pro."
The AI checks which card works at Cursor and asks for a one-time card of $20.
You get a Telegram message and tap Approve.
The AI fills the checkout with the one-time card. The card freezes after the payment.
Cards work for subscriptions and normal online purchases. They cannot top up developer API credit balances (for example the OpenAI or Anthropic consoles).
Never paste your plugin key into a chat. If a key leaks, revoke it on the member page and create a new one.
Questions: tunapay.ai
MIT
This server cannot be deployed
Prepaid virtual cards for AI agents: one-time cards, spend caps, human approvals.
Let your AI assistant pay for web content in USDC (x402) within a budget you set.
Payment infrastructure for AI agents: spending rules, approval flows, single-use virtual cards.
Give your AI agent a spending limit: approval controls and single-use virtual cards.
