Language:JapaneseEnglish

mercadopago Claude Code Plugin

Author
Mercado Pago Developer Experience
Category
Development
Topics
Payments & Fintech · Web & App Development · Security, Auth & Compliance
First cataloged
2026-07-09 (UTC)
Explanation last updated
2026-09-22 (UTC)
Source (GitHub) last updated
2026-08-27 (UTC) (49 days ago)

The explanation below is AI-generated. Please verify it against the sources.

This plugin is a Claude Code toolkit that helps developers integrate Mercado Pago's payment products into their applications. According to its README, a single router agent examines the target country and integration mode, then hands off work to one of four specialized skills: an integration wizard, a webhooks helper, a test-account setup helper, and a review/audit helper. Code scaffolding, bundled test cards, and local security checks work without any account connection, drawing on bundled reference material and per-country documentation snippets. The plugin only initiates an OAuth connection to the official Mercado Pago MCP server when a specific operation requires live data, such as fetching current documentation, importing credentials, creating test users, registering webhooks, or running official quality/homologation checks. It also ships a hook that scans code edits for hardcoded Mercado Pago credentials and restricts access to environment files in detected projects.

About the service

Mercado Pago is a payment platform, primarily serving Latin American markets, that lets individuals and businesses process online and in-person payments, hold a digital wallet, generate QR codes and payment links, use point-of-sale card readers, offer subscription billing, and access credit and currency-related services. The plugin's MCP-backed operations connect to this platform's official server to fetch documentation, manage test accounts, and configure webhooks and quality checks.

What you can do with mercadopago

  • Have a router agent detect your target country and integration mode, then delegate to the matching skill
  • Set up and validate webhook receivers using HMAC-SHA256 signature checks, and inspect notification history through the MCP server
  • Create test user accounts and load test funds using the appropriate credential formats
  • Run a local security review of the integration and, when needed, request official quality checklist, evaluation, and homologation results via MCP
  • Pull bundled test card data for a given country without requiring any live connection
  • Rely on a built-in hook that flags hardcoded payment credentials in code and blocks accidental exposure of environment files

Sources

Back to list