AI tools (MCP)
Connect Mono's documentation to Claude, Cursor, and other AI assistants so they can answer integration questions — and run Bre-B and Core sandbox calls — while you build.
Mono publishes an MCP server for this documentation. MCP (Model Context Protocol) is an open standard that lets AI assistants — like Claude or Cursor — plug into outside tools and data. Connect Mono's MCP and your assistant can search these docs, open full pages, and pull ready-made integration recipes while you code. When you opt in, it can also run real calls against the Bre-B and Core sandboxes — safe test environments that never move real money — so you can try an integration end to end without leaving your editor.
It answers from the same documentation you are reading now and links back to the source, so the guidance stays grounded and current — not invented.
Before you start
You will need:
-
An AI tool that supports MCP — for example Claude Code or Cursor.
-
For live sandbox calls only (optional): sandbox credentials for the product you want to test. Each product authenticates differently:
- Bre-B (Colombia's instant-payment network) — your sandbox
client_idandclient_secretfrom the Mono dashboard, with the Bre-B scopes enabled (collections, outgoing transfers, target resolutions, tenant accounts). The MCP signs in with them and requests those scopes; if one is missing, the sandbox calls are rejected. - Core (programmable ledger and card issuing) — a Core sandbox API token that Mono generates for you. The MCP forwards it on each call.
You can add Bre-B, Core, or both — the assistant gains each product's tools when its credentials are present.
- Bre-B (Colombia's instant-payment network) — your sandbox
What your assistant can do
Reading the docs needs nothing; running calls needs the matching sandbox credentials.
Read the docs (no credentials):
- search the documentation by meaning, not just keywords;
- open any page in full;
- get a step-by-step integration guide for a use case;
- get the exact API reference for an endpoint — request and response examples, fields, and allowed values.
Run Bre-B sandbox calls: create a collection, simulate a payment to it, resolve a payment key, and send an outgoing transfer.
Run Core sandbox calls: manage the ledger (accounts, balances, transfers) and issue and manage cards (cardholders, cards, spending controls, activation).
Connect to read the docs
This mode is hosted by Mono and needs no credentials. In Claude Code:
claude mcp add --transport http mono-docs https://docs.cert.monoban.co/api/mcpOther MCP clients (Cursor, etc.) connect to the same URL over HTTP (also called "Streamable HTTP"). Then just ask, in plain language:
How do I receive my first Bre-B payment? Show me the create-collection request.
Your assistant searches the docs, pulls the integration guide and the exact endpoint, and answers with working code and links to the source pages.
Run live sandbox calls (optional)
This is the same hosted MCP — you add credential headers when you connect, and your assistant gains that product's tools on top of the docs tools. Credentials travel on the connection itself, never inside a question, so they stay out of your chat and out of the logs; Mono uses them to sign each call and then discards them.
Bre-B
In Claude Code, add the two credential headers:
claude mcp add --transport http mono-docs https://docs.cert.monoban.co/api/mcp \
--header "X-Mono-Client-Id: <your sandbox client_id>" \
--header "X-Mono-Client-Secret: <your sandbox client_secret>"Then drive it in plain language. Start read-only to confirm the connection:
List my Bre-B tenant accounts.
Then walk the full flow:
Create a Bre-B collection for COP 50,000, simulate a payment to it, and confirm it is paid.
Core
Add your Core sandbox token header:
claude mcp add --transport http mono-docs https://docs.cert.monoban.co/api/mcp \
--header "X-Mono-Core-Token: <your Core sandbox token>"Then, again starting read-only:
List my Core ledger accounts.
And the full flow:
Create a cardholder, issue a card against a ledger account with a spending control, then show me the card.
Both at once
To use Bre-B and Core tools on the same connection, add all three headers:
claude mcp add --transport http mono-docs https://docs.cert.monoban.co/api/mcp \
--header "X-Mono-Client-Id: <client_id>" \
--header "X-Mono-Client-Secret: <client_secret>" \
--header "X-Mono-Core-Token: <core token>"If you already connected for docs only, re-add it with these headers to enable the sandbox tools.
Sandbox only. Live calls can only reach Mono's sandbox — never production, never real money. Credentials are used per call and never stored, and any sensitive card data Core returns in the sandbox is synthetic test data, not a real card.
Next steps
- Bre-B collections (Recaudo) — receive your first payment.
- Bre-B outgoing transfers — send a payout.
- Issuing cards (Core) — issue and manage cards.
- Technical support — reach the Mono team.