The search-documentation tool allows you to search for information directly in Mercado Pago's official documentation.

When using the assistant and making a request in natural language, you can search for information in the documentation and access it according to each stage of development. For example, checking which payment methods are available in a specific country.

plain
Copiar
Search Mercado Pago documentation for available payment methods.

In addition to consulting the documentation, the tool search-documentation also allows you to generate code for your project.

You can request this recommendation from the assistant by asking it to review the documentation of the product you want to integrate and indicate the necessary steps to perform this integration. The MCP Server provides the necessary context, through code and documentation, so that the IDE can make the required modifications to your project.

For this use case, let's consider a store that's already configured and only needs to integrate a checkout to start processing payments. In this context, a guidance prompt for integrating with Checkout Pro could be:

plain
Copiar
Implement Checkout Pro integration. 
Query the Mercado Pago MCP Server documentation for any implementation details or uncertainties.

After reviewing existing application code, generate production-ready code as follows:

Frontend:
1. Replace current checkout UI with Mercado Pago checkout interface;
2. Handle payment form integration;
3. Implement client-side success/failure flows.

Backend:
1. Set up credentials and SDK integration in the most recent version;
2. Create payment processing endpoints;
3. Implement webhook handling with validations.

Requirements:
- Mercado Pago security best practices and validation;
- Error handling with status codes;
- Test cases for critical flows;
- Inline documentation;
- Verify all steps against Mercado Pago MCP Server documentation.

The result may vary depending on your project configuration, but as a general rule, the Mercado Pago MCP Server will suggest code modifications in the frontend and backend of your integration to create the checkout.

If you want to see more details of this practical example, check out our Medium article about the success case of integrating Checkout Pro in 30 minutes.

You can combine tools to configure Mercado Pago Webhook notifications and test their proper functioning before going to production.

In the following example, we combine the use of the search_documentation, save_webhook, and simulate_webhook tools to perform a complete configuration, from implementing a receiver to simulating a delivery, thus confirming the operation of the entire flow.

plain
Copiar
I'm developing an integration with Mercado Pago and need to configure and test webhook notifications for payments.

Follow these instructions to meet my goal:

1. Consult the official Mercado Pago documentation to identify the technical and security requirements that a webhook notification receiver must meet.

2. Based on that information, generate a functional implementation example adapted to my project to receive and process notifications.

3. Configure Mercado Pago webhook notifications for payments, pointing to the test URL <webhook.site>.

4. Simulate a payment event to validate that the receiver processes them correctly.

Mercado Pago MCP Server can assist you in implementing improvements to your integration, so it can adapt to the quality and security standards required for operating with Mercado Pago.

Combine the quality_checklist and quality_evaluation tools to ensure a development according to these standards and best practices, and then measure the quality of your integration with a real payment, once you have gone to production.

To do so, use a sequence of prompts similar to the example below.

plain
Copiar
I want to ensure that my integration code implements maximum quality, maintainability, efficiency, and approval rate. For this, I need you to perform an exhaustive analysis of its quality, where you will identify areas for improvement and implement concrete solutions that optimize performance and adherence to Mercado Pago standards.

Follow these instructions to implement these improvements:

1. Review the source code, understand its structure, and identify where the Mercado Pago integration is located.
2. Consult the Mercado Pago documentation and create a list of best practices and quality requirements to improve my integration taking into account Mercado Pago standards.
3. Implement the improvements that are required or that will be evaluated by Mercado Pago.
4. Generate a summary of the applied changes and include at the end those best practice suggestions that can be included in the integration.
5. Tell me how to make a production payment to verify that these changes are effective.

Once you have the productive payment, you can ask the agent to perform a quality measurement using the new payment identifier.

plain
Copiar
Measure the quality of my Mercado Pago integration using payment_id <yournewpaymentid> as reference.

Mercado Pago MCP Server tools will help you obtain a complete guide to properly test your integration in one place, also assisting you in creating test users.

In this example, the search_documentation and create_test_user tools are combined to have everything needed for a complete integration testing flow of QR Code without leaving the development environment.

plain
Copiar
**Context:**

You are integrating the dynamic model QR Code flow using Mercado Pago's Orders API and need to test this integration with an end-to-end simulation, respecting real testing conditions.

**Model role:**

Act as a technical documentation and code generator that strictly follows official Mercado Pago documentation.

**Specific task:**

Generate a structured and detailed response that includes:

1. **Integration testing control:**
Use exclusively the official Mercado Pago documentation to detail the necessary requirements to test the dynamic model QR Code flow with Orders API. Clearly indicate which type of credentials should be used (test vs. production) at each stage.

2. **Test user creation:**
Create test users:
* A seller from Argentina with credentials, labeled as `orders testing`.
* A buyer labeled as `orders buyer`.

3. **Step-by-step payment simulation:**
Provide concise instructions to simulate the complete flow from order creation to payment completion, using only official documentation.
* Break down each key action.
* Explain the logical order of operations and their justification.

**Restriction:**

Do not generate or assume data outside official documentation. If specific information is missing, clearly indicate this and suggest verifiable alternatives or official resources.

**Expected result:**

A guide with well-differentiated sections, example code or JSON if applicable, and precise technical explanations, ready to be used as a testing base in an integration environment.