MCP server for AI agents

Connect

Server URL (Streamable HTTP):

https://pay.snapex.pro/mcp

No key is needed to start: the agent calls create_account and goes on with its new key in the same session. Configs for popular clients:

Claude Code

claude mcp add --transport http snapex-pay https://pay.snapex.pro/mcp

Cursor — ~/.cursor/mcp.json

{
    "mcpServers": {
        "snapex-pay": {
            "url": "https://pay.snapex.pro/mcp"
        }
    }
}

VS Code — .vscode/mcp.json

{
    "servers": {
        "snapex-pay": {
            "type": "http",
            "url": "https://pay.snapex.pro/mcp"
        }
    }
}

Windsurf — ~/.codeium/windsurf/mcp_config.json

{
    "mcpServers": {
        "snapex-pay": {
            "serverUrl": "https://pay.snapex.pro/mcp"
        }
    }
}

Claude Desktop — claude_desktop_config.json

{
    "mcpServers": {
        "snapex-pay": {
            "command": "npx",
            "args": [
                "-y",
                "mcp-remote",
                "https://pay.snapex.pro/mcp"
            ]
        }
    }
}

claude.ai and ChatGPT connectors

Add a custom connector with the server URL. These clients cannot send headers, so after create_account take mcp_personal_url from its answer and use it as the connector URL — it keeps the same account in every new chat. Treat that URL as a password.

Already have a key

Add the header Authorization: Bearer smk_… — the merchant key from the cabinet (Merchant → Developers) or from create_account.

{
    "mcpServers": {
        "snapex-pay": {
            "url": "https://pay.snapex.pro/mcp",
            "headers": {
                "Authorization": "Bearer smk_…"
            }
        }
    }
}

How an agent works with it

Connect the URL — no key needed.
The agent calls create_account: no captcha, no email. It gets a key with every scope, and the session goes on with it.
To get paid: create_invoice → the payer opens pay_url → get_invoice shows paid. Payments are credited to the balance in USDT.
To pay out: preview_payout shows the amount and fee, create_payout sends — in any coin from list_assets.

Tools

The same tools in the remote server and the local package. Each answer is JSON; an error says what to do next.

Account

create_account, get_account

Coins, rates and fees (no key needed)

list_assets, get_fiat_rates, get_fees, list_static_address_networks

Balance and history

get_balances, list_transactions

Receive: invoices, payments, permanent addresses

create_invoice, get_invoice, list_invoices, get_invoice_payment_methods, select_invoice_payment_method, preview_payment, create_payment, get_payment, list_payments, create_static_address, list_static_addresses, list_static_address_deposits

Send: payouts

preview_payout, create_payout, get_payout, list_payouts

Exchange: conversions

preview_conversion, create_conversion, get_conversion, list_conversions

Webhooks

list_webhooks, create_webhook, update_webhook, rotate_webhook_secret

Safety

The key and the generated password are shown once, in the answer of create_account. A person can open the cabinet with the login and password.
An agent moves only its own account's money. A new account starts at zero; money arrives from payments to its invoices and addresses.
Sending is two steps: preview_payout shows the amount and fee, create_payout sends with the agent's own idempotency_key — a retry never pays twice.
Test mode: an invoice with environment test goes through the whole flow without real money.
Limits: a few new accounts per IP per hour; payouts — 5 a minute and 30 an hour per key.
What can and cannot be sold: Rules

Without MCP

The same works over the REST API: an account in one request, then the Merchant API with the key.

curl -X POST https://pay.snapex.pro/api/v1/merchant/signup -H 'Content-Type: application/json' -d '{"agent":"my-agent"}'

API docs · llms.txt · mcp.json