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., "@cryptunnel-mcp create a sandbox payment for 10 USD for order test-1 and give me the checkout link"
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.
An MCP server that lets a coding agent - Claude Code, Cursor, anything speaking the Model Context Protocol - create and look up Cryptunnel crypto payments. Build a payment integration by prompting: "create a sandbox payment for 10 USD and give me the checkout link".
It runs on your machine over stdio, wraps the cryptunnel
client, and talks to nothing but api.cryptunnel.io. No hosted service, no OAuth.
You need your merchant id and an API key, both from the merchant page in the cabinet. Node 20+.
claude mcp add cryptunnel \
--env CRYPTUNNEL_MERCHANT_ID=<merchant id> \
--env CRYPTUNNEL_API_KEY=<api key> \
-- npx -y cryptunnel-mcpOr, to share it with a project, in .mcp.json at the repository root:
{
"mcpServers": {
"cryptunnel": {
"command": "npx",
"args": ["-y", "cryptunnel-mcp"],
"env": {
"CRYPTUNNEL_MERCHANT_ID": "<merchant id>",
"CRYPTUNNEL_API_KEY": "<api key>"
}
}
}
}In .cursor/mcp.json (per project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptunnel": {
"command": "npx",
"args": ["-y", "cryptunnel-mcp"],
"env": {
"CRYPTUNNEL_MERCHANT_ID": "<merchant id>",
"CRYPTUNNEL_API_KEY": "<api key>"
}
}
}
}Create a sandbox payment for 10 USD for order
test-1and give me the checkout link.
The agent calls create_payment, and the link opens the checkout page listing testnet coins. If the
list is empty, attach a testnet wallet to the merchant in the cabinet first - see
Sandbox and faucets.
Related MCP server: @chainpayto/mcp-server
Variable | Meaning |
| Your public merchant id. Required - the server exits naming it when missing |
| Your API key. Required |
| Set to |
| Point the server at another API host, for a local backend |
An agent holding a live key must not be one prompt away from a real invoice. So by default every
payment this server creates is a sandbox payment: the buyer is offered testnet coins only, nothing
is charged, and the payment stays out of your stats. Asking for is_test: false is refused with a
message that names the variable - the payment is not silently downgraded, the agent is told why.
Set CRYPTUNNEL_ALLOW_LIVE=1 to let the agent create real payments. Even then a payment is a
sandbox one unless the agent passes is_test: false explicitly.
Tool | What the agent gets |
| A checkout url for a given amount and currency, keyed by your |
| One payment by id, with its status - deliver on |
| The merchant's payments, newest first, paged |
| The currencies the merchant can receive - only those with an active wallet |
Every tool returns the API response as JSON text; an API error comes back as a tool error carrying
the API code, e.g. ValidationError (WALLET_NOT_FOUND): Wallet not found.
cryptunnel client the server wraps
Support: GitHub Issues
MIT licensed.
This server cannot be deployed
Keyless non-custodial crypto payments for AI agents: payment links and tip jars, no API key.
Non-custodial crypto payments for AI assistants: balances, payments, and create payment links.
Stripe payments for AI agents. Create links, verify, manage customers.
Let AI agents add Yolfi crypto checkout, paylinks, webhooks, and status checks.
