Openpay

What your agent can do

Openpay gives your agent 23 tools it calls directly — pick the ones it needs, in Claude, Cursor, or any MCP client.

• →create_charge — Create a charge. Pass customer_id to charge at a customer scope (POST /customers/{customer_id}/charges); omit to charge at merchant scope (POST /charges). Methods: 'card' (requires source_id token), 'bank_account' (SPEI — returns CLABE reference), 'store' (OXXO — returns barcode/reference). Amounts are in major units (e.g. 100 = 100 MXN).
• →get_charge — Retrieve a charge. Pass customer_id to fetch at customer scope (GET /customers/{customer_id}/charges/{id}); omit for merchant scope (GET /charges/{id}).
• →capture_charge — Capture a previously authorized charge (when the original charge used capture=false). Pass amount to capture less than the authorized total; omit to capture the full authorized amount.

// Your agent calls a tool directly — no glue code.
// CodeSpar's managed tier handles OAuth2, token rotation and rate limits.
const result = await session.call("create_charge", { /* ... */ });

Install

$ npm install @codespar/mcp-openpay

Quickstart

Add this entry to your claude_desktop_config.json (or any MCP-compatible client config).

{
  "mcpServers": {
    "openpay": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-openpay"
      ],
      "env": {
        "OPENPAY_MERCHANT_ID": "<your_openpay_merchant_id>",
        "OPENPAY_PRIVATE_KEY": "<your_openpay_private_key>"
      }
    }
  }
}

After restart, your agent can call any of the 23 tools below — try create_charge first.

Environment variables · 3

Required to authenticate the server. Stored encrypted when using CodeSpar managed hosting.

Available tools · 23

Each tool is independent — your agent loads only what it needs to reduce context and response time.

Compatible frameworks

MCP is a protocol — any framework that speaks it can mount this server.

Frequently asked questions