Clip

Mexico's leading native acquirer. Inbound charges via hosted payment links or transparent checkout, so your agent charges MX cards without local paperwork.

MIT · runs locally with your own credentials

Quickstart

Install, set the credentials, make the first call.

Pick your client. The server runs locally over stdio, with your own credentials.

Tools

What your agent can call.

Create a hosted checkout / payment link (POST /v2/checkout). The buyer opens the returned payment_request_url and pays with card, Clip account or other enabled MX methods. Amount is in MXN pesos (decimal, e.g. 150.00).

Fetch a checkout / payment link by id (GET /v2/checkout/{id}) — status, amount, payment outcome.

Create a transparent card charge (POST /payments) using a card token generated by Clip's client-side SDK. Use create_payment_link instead when you have no tokenization front-end — raw card numbers are never accepted here.

Fetch a payment by id (GET /payments/{id}) — status, amounts, card summary, refunds.

List payments (GET /payments), newest first. Paginated via limit/offset.

Refund a payment (POST /payments/{id}/refund). Omit amount for a full refund; pass it for a partial refund in MXN.

Compatibility

MCP is a protocol. Any client that speaks it can mount this server.

codespar_discover lists this server's tools, but a project with a test key cannot call them: the provider has no test environment, so the runtime refuses test-mode calls.

Start in seconds.

Add the config above, set the variables, and your agent calls the tools.