post cover image

Mercado Pago MCP Server: new tools for your IDE

Mercado Pago MCP Server is expanding to further simplify the development process with the new Notifications and Integration Quality tools.

Designed to remove common integration frictions directly from your IDE, you can now configure Webhooks, simulate notifications, validate quality standards, and diagnose errors without leaving the environment where you build and test your application.

Together with the search_documentation tool, you can develop your Mercado Pago project end-to-end.

1. Design

  • search_documentation: generates code tailored to your project based on queries to Mercado Pago’s official documentation.
  • quality_checklist: returns the requirements and best practices that Mercado Pago evaluates in an integration. It serves as the foundation to plan which points to cover before going live.

2. Alerts configuration

  • save_webhook: sets up or updates Webhook notifications with test or production URLs, allowing you to select the notification topics.
  • simulate_webhook: sends simulated notifications to your backend using a resource_id, enabling you to validate the reception logic before handling real notifications.

3. Validation in production

  • quality_evaluation: takes a production payment_id and evaluates integration quality based on actual behavior, returning a score and adjustment suggestions.

4. Monitoring and continuous improvement

  • notifications_history_diagnostics: analyzes the notification history sent to your application, with delivery metrics and reports in case of failures. It is the key tool to identify recurring issues and strengthen your system in production.

Moreover, you can combine these tools to expand their functionalities according to your needs. In the Use cases section, we showcase just a few of these options, with ready-to-try prompt examples.

If you haven’t set up Mercado Pago MCP Server yet, now is a great time: centralize your integration in your IDE, reduce sync errors, and avoid unnecessary environment changes. Check how to configure it in Cursor and Windsurf, or check lathedocumentation for other IDEs.