Use cases

The /mp-integrate command is the main entry point of the plugin for completing an integration through AI agents. Through a conversational interaction, it automatically detects the product and country mentioned in your message and generates the necessary integration code, without requiring you to search for documentation.

You can build integration flows for the seven countries where Mercado Pago operates (Argentina, Brazil, Mexico, Chile, Colombia, Peru, and Uruguay), and for the main integrable products, such as Checkout API, Checkout Pro, Código QR, and Mercado Pago Point.

To get started, run the command followed by a description of what you need to integrate. The more context you include, the more specific the code you receive. Some examples:

plain
/mp-integrate I want to integrate Checkout Pro in Brazil

plain
/mp-integrate I need to accept QR Code payments in Brazil for my retail app

plain
/mp-integrate how do I add monthly subscriptions for my users in Mexico

When execution finishes, the plugin delivers:

• Integration code: implementation adapted to the language or framework you indicated in the command. You can request versions in other languages within the same session.
• Configuration snippets: SDK initialization or API call structure for the selected product.
• Payload examples: request bodies with the relevant parameters for the product and country.
• Parameter guidance: indication of which fields are required or optional, with example values.

/mp-integrate works in two distinct modes depending on your session's authentication state:

The /mp-webhooks command lets you configure, simulate, and diagnose Mercado Pago Webhook notifications within your AI agent session. To use it, you must authenticate through /mp-connect.

You can run the following subcommands:

• /mp-webhooks configure: registers your endpoint's HTTPS URL and the event topics you want to receive, such as order, topic_claims_integration_wh, or topic_chargebacks_wh.
• /mp-webhooks simulate: sends a test notification to the configured endpoint to validate that the HMAC-SHA256 signature is being processed correctly.
• /mp-webhooks status: checks the registration status and identifies URL or topic issues.
• /mp-webhooks diagnose: diagnoses signature and delivery failures.

The plugin covers both steps to prepare your test environment: getting test cards with /mp-test-cards and creating users with balance with /mp-test-setup.

Start by running /mp-test-cards to get the test cards available for your country. This command does not require authentication.

plain
/mp-test-cards

In the test payment form, the cardholder name determines the simulation result, so follow the pattern of APRO (approved), FUND (insufficient funds), CONT (pending), SECU (invalid CVV), and EXPI (expired card). In the DNI field, use document number 12345678.

After configuring your test cards, run the /mp-test-setup command to create a seller and a buyer user with test credentials and available balance. This command only works after OAuth authentication (/mp-connect).

plain
/mp-test-setup

The expected outcome is having your users available to start testing.

The /mp-review command analyzes your integration's code against a quality checklist and a 9-criteria Mercado Pago minimum security standard to generate an implementation report with suggested actions to improve your development. This command requires an active session, so run /mp-connect before using it.

The implementation report is organized into 5 sections:

1. Verified: checklist items already implemented correctly.
2. Needs attention: partial implementations that need adjustments.
3. Blockers: critical issues that prevent going to production.
4. Next steps: optional improvements to raise your integration's quality.
5. Score and verdict: final result, whether approved, approved with remarks, or blocked.

/mp-review also detects Access TokensPrivate key of the application, used in the backend to authenticate calls to the Mercado Pago API. You can access it under Your integrations > Application details > Credentials. exposed in the source code and identifies direct calls to the /v1/payments endpoint that could benefit from migrating to the Orders API.

/mp-integrate migrate scans the project, identifies legacy Payment Intent API patterns from Mercado Pago Point and/or Código QR, and generates the migration-proposal.md file with a complete breakdown of the changes and the migration instructions for the Orders API.

The migration proposal file covers the main points for adapting to the Orders API, such as:

• state field to status;
• merchant_order and point_integration_wh notification topics to orders;
• external_reference field with hyphens;
• Removal of the X-Allow-Cancelable-Status header;
• Inclusion of MP_WEBHOOK_SECRET in .env.example.

After reviewing and applying the proposed changes, run /mp-review to validate that the migrated integration meets the quality checklist before going to production.