概览
What is Colombia Payments Mcp?
Colombia Payments Mcp is a remote MCP (Model Context Protocol) server that enables any AI agent (Claude, ChatGPT, Cursor, etc.) to accept payments in Colombia via Mercado Pago's hosted checkout. It supports PSE bank transfers, Nequi, credit/debit cards, and Efecty cash. The server is a stateless translation layer: funds flow directly from buyer to Mercado Pago to the merchant – it never holds funds, stores credentials, or uses a database.
How to use Colombia Payments Mcp?
Configure your MCP client (e.g., Claude, Cursor) with the endpoint https://mcp-co.wishpool.app/mcp and set the header x-mercadopago-access-token to your Mercado Pago access token (use TEST- for test mode, APP_USR- for production). Available tools are create_payment_link (generates a COP hosted‑checkout link) and query_payment_status (pull‑based status check; returns paid=true when paid).
Key features of Colombia Payments Mcp
- Remote MCP server for AI agents
- Accepts PSE, Nequi, cards, Efecty payments
- Stateless: no database or credential storage
- Pull‑based payment status verification
- Zero runtime dependencies; requires Node ≥ 18
- Streamable HTTP transport (JSON‑RPC)
Use cases of Colombia Payments Mcp
- Let an AI assistant generate a checkout link for a Colombian customer
- Verify payment status programmatically from an agent workflow
- Integrate Colombian payment methods into an AI‑powered e‑commerce bot
- Offer local payment options (nequi, PSE) via a chat interface
FAQ from Colombia Payments Mcp
How does this compare to building a custom payment integration?
Colombia Payments Mcp is a stateless translation layer that connects an AI agent to Mercado Pago’s hosted checkout. It never holds funds, stores credentials, or processes payments itself – all money goes directly from buyer to Mercado Pago to the merchant.
What runtime does it need?
Node.js version 18 or higher. The server itself has zero runtime dependencies.
Where is payment data stored?
No data is stored. The server is fully stateless – it translates requests and responses between the AI agent and Mercado Pago without persisting any information.
What transport and authentication does it use?
It uses Streamable HTTP (stateless JSON‑RPC). Authentication is via the x-mercadopago-access-token header; supply your Mercado Pago access token (test or production) as the header value.
Are there any known limitations?
The server is remote and always requires an internet connection. It relies on Mercado Pago’s availability and requires a valid access token. There is no built‑in retry or webhook mechanism – status must be polled via query_payment_status.
