MCP Server

CBPay ships an official MCP (Model Context Protocol) server at https://mcp.cbpayapp.com. Add it to Cursor, VS Code, Claude or any MCP-compatible client and your AI assistant can search this documentation, read every endpoint with its real request/response examples and look up error codes — without leaving your editor. It is documentation only and read-only: it never calls the live API, never needs an API key, and requires no authentication. The transport is streamable HTTP.

One-click install

Setup by client

Click the Add to Cursor button above and confirm the install, or add the server manually to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project:

mcp.json

{
  "mcpServers": {
    "cbpay-docs": {
      "url": "https://mcp.cbpayapp.com"
    }
  }
}

The server appears in Settings → MCP with its tools ready to use.

One command from your terminal:

claude mcp add --transport http cbpay-docs https://mcp.cbpayapp.com

Verify with claude mcp list — cbpay-docs should show as connected.

On claude.ai or in Claude Desktop:

Open Settings → Connectors.
Click Add custom connector.
Name it cbpay-docs and paste the URL https://mcp.cbpayapp.com.
Save — no authentication step is required.

Click the VS Code button above, or add the server manually to your user mcp.json (Command Palette → MCP: Open User Configuration):

mcp.json

{
  "servers": {
    "cbpay-docs": {
      "type": "http",
      "url": "https://mcp.cbpayapp.com"
    }
  }
}

GitHub Copilot Chat (agent mode) picks up the tools automatically.

In ChatGPT (paid plans, with developer mode enabled):

Open Settings → Connectors → Advanced → Developer mode.
Click Create and paste https://mcp.cbpayapp.com as the MCP server URL.
Set authentication to None and save.

Any MCP client that supports remote servers over streamable HTTP works. The generic configuration is:

{
  "mcpServers": {
    "cbpay-docs": {
      "url": "https://mcp.cbpayapp.com"
    }
  }
}

No API key, no headers, no OAuth — just the URL.

Available tools

Tool	What it does
`search_docs`	Searches the documentation (sections and endpoints) and returns results ranked by relevance
`list_sections`	Lists the table of contents with each section id and group
`get_section`	Returns the full markdown of a section, including its subsections
`list_endpoints`	Lists the documented endpoints, filterable by group and/or HTTP method
`get_endpoint`	Returns the documentation of one endpoint with its curl, request and response examples
`list_groups`	Lists the products/groups (payouts, payins, banking, crypto, …) with their endpoint counts
`get_errors_catalog`	Returns the API error catalog (HTTP code, `error` code, meaning and category), filterable by text

Prompts to try

Once connected, ask your assistant things like:

“Using the CBPay docs, show me how to create a payout to Chile with curl.”
“What does the idempotency_key_required error mean and how do I fix it?”
“List every payins endpoint and explain the QR flow for Bolivia.”
“How do I verify the signature of a CBPay webhook?”

FAQ

Do I need an API key or account?

No. The MCP server is public and serves documentation only. Your CBPay API key is never involved — keep it for your integration code.

Can it execute operations against my account?

No. The server is strictly read-only over documentation content: it cannot create payouts, move balances or touch the live API in any way.

Which transport does it use?

Streamable HTTP at https://mcp.cbpayapp.com. Clients that only support stdio-based local servers can bridge it with a proxy such as mcp-remote.

How is this different from Postman or the site search?

Same content, different consumer: the Postman collection is for humans testing requests, the site search is for humans reading — the MCP server is for your AI assistant, so it can answer integration questions with the real documented behavior instead of guessing.

Is the content always up to date?

Yes — it is generated from the same documentation you are reading, so every release listed in the changelog is reflected in the MCP content as well.

Getting Started

Concepts

Integration flows

Products

Integration

Resources

One-click install

Setup by client

Available tools

Prompts to try

FAQ

​One-click install

​Setup by client

​Available tools

​Prompts to try

​FAQ

One-click install

Setup by client

Available tools

Prompts to try

FAQ