Openpay MCP server

Read from the package source without running it. The installed server may list more.

• cancel_subscriptionwrite action

  Cancel a customer's subscription (DELETE /customers/{customer_id}/subscriptions/{id}). Cancellation takes effect at the end of the current paid period.

• capture_chargewrite action

  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.

• create_bank_accountwrite action

  Store a customer bank account (POST /customers/{customer_id}/bankaccounts). Required before you can run destination_id-based payouts to that customer's account.

• create_cardwrite action

  Tokenize a card. Pass customer_id to attach to a stored customer (POST /customers/{customer_id}/cards); omit for a merchant-level token (POST /cards). Prefer tokenizing client-side with Openpay.js to avoid PCI scope.

• create_chargewrite action

  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).

• create_customerwrite action

  Create a customer record. Set requires_account=true to create an associated Openpay wallet for the customer; false for a payment-only record.

• create_payoutwrite action

  Pay out MXN to a bank account. Used for marketplace seller payouts and cross-border settlement. Scope to a customer with customer_id (POST /customers/{customer_id}/payouts) or run at merchant scope (POST /payouts).

• create_planwrite action

  Create a subscription plan. Plans are templates — use create_subscription to subscribe a customer.

• create_subscriptionwrite action

  Subscribe a customer to a plan. Requires a stored card (source_id) to charge on each cycle.

• create_webhookwrite action

  Register a webhook endpoint (POST /webhooks). Openpay posts event notifications to url and can optionally send HTTP Basic credentials.

• delete_bank_accountwrite action

  Delete a stored customer bank account (DELETE /customers/{customer_id}/bankaccounts/{id}).

• delete_cardwrite action

  Delete a tokenized card. Pass customer_id to delete at customer scope (DELETE /customers/{customer_id}/cards/{id}); omit for merchant scope (DELETE /cards/{id}).

• delete_customerwrite action

  Delete a customer (DELETE /customers/{id}). Irreversible — removes the customer and associated stored tokens.

• delete_webhookwrite action

  Delete a webhook subscription (DELETE /webhooks/{id}).

• get_card

  Retrieve a tokenized card. Pass customer_id to fetch at customer scope (GET /customers/{customer_id}/cards/{id}); omit for merchant scope (GET /cards/{id}).

• get_chargewrite action

  Retrieve a charge. Pass customer_id to fetch at customer scope (GET /customers/{customer_id}/charges/{id}); omit for merchant scope (GET /charges/{id}).

• get_customer

  Retrieve a customer by Openpay customer id.

• list_cards

  List tokenized cards. Pass customer_id to list per-customer (GET /customers/{customer_id}/cards); omit for merchant-level cards (GET /cards).

• list_customers

  List customers with optional filters. All parameters are passed as query params.

• list_payouts

  List payouts. Pass customer_id to scope to a customer (GET /customers/{customer_id}/payouts); omit for merchant-scope payouts (GET /payouts).

• list_webhooks

  List configured webhook subscriptions (GET /webhooks).

• refund_chargewrite action

  Refund a captured charge. Supports partial refunds via amount; omit amount for a full refund.

• update_customerwrite action

  Update a stored customer (PUT /customers/{id}). Only the fields provided are updated; omit fields you don't want to change.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 29 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

82/100

higher than 63% of 48,255 servers

Tools

23

the typical server has 7

Tools that change things

74%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

271

more than 95% of 28,688 servers

Openpay: common questions

Is Openpay MCP server safe?

Mostly: it is graded B (82/100). Read the Openpay safety report

How do I install Openpay?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Openpay need an API key?

Yes. The registry entry asks for OPENPAY_PRIVATE_KEY.

Is Openpay maintained?

The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.

How does Openpay compare with other MCP servers?

safety score 82/100 (higher than 63% of 48,255 servers); tools 23 (the typical server has 7); tools that change things 74% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.