TgPay Merchant API MCP MCP server

This MCP server enables AI agents to integrate with the TgPay Merchant API, allowing for the creation of merchant apps, generation of crypto invoices, management of subscriptions, and handling of payouts and webhooks directly through Telegram.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by TG Crypto Pay

MCP endpoint (Streamable HTTP)

https://app.tgpaycrypto.com/mcp

Vendor documentation

What you can do with it

Create merchant apps and generate API tokens
Issue crypto invoices to Telegram users
Set up recurring subscription billing plans
Configure webhooks for payment events

Tools advertised by the last live check:

get_docs
connect
connect_status
getMe
getBalance
getCurrencies
getExchangeRates
getStats
getInvoices
getChecks
getTransfers
getSubscriptionPlans
getSubscriptions
createInvoice
deleteInvoice
deleteCheck
createSubscriptionPlan
archiveSubscriptionPlan
cancelSubscription
updateApp

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http tgpay-merchant-api-mcp https://app.tgpaycrypto.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add tgpay-merchant-api-mcp --url https://app.tgpaycrypto.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tgpay-merchant-api-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "tgpay-merchant-api-mcp": {
      "url": "https://app.tgpaycrypto.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "tgpay-merchant-api-mcp": {
      "type": "streamableHttp",
      "url": "https://app.tgpaycrypto.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tgpay-merchant-api-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "tgpay-merchant-api-mcp": {
      "type": "http",
      "url": "https://app.tgpaycrypto.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http tgpay-merchant-api-mcp https://app.tgpaycrypto.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "tgpay-merchant-api-mcp": {
      "url": "https://app.tgpaycrypto.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "tgpay-merchant-api-mcp": {
      "serverUrl": "https://app.tgpaycrypto.com/mcp"
    }
  }
}

See all 128

Do you run TgPay Merchant API MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing