Hosting

Remote hosted

Transport

Streamable HTTP

Endpoint

https://mcp.mercadopago.com/mcp

Authentication

OAuth browser authorization is the documented client flow; select operating country and grant permissions. Vendor troubleshooting also documents an `Authorization: Bearer <ACCESS_TOKEN>` alternative. Application tools require OAuth.

Requirements

• Mercado Pago account and valid credential for relevant country/site
• MCP-compatible client; vendor lists Cursor 1+, VS Code, Windsurf, Cline, Claude Desktop/Code, and ChatGPT
• Node.js 20+ and npx for common client configurations/troubleshooting proxy flow

Setup steps

1. Add https://mcp.mercadopago.com/mcp as remote MCP server.
2. Enable/connect it and complete browser authorization on Mercado Pago's site; select country and review permissions.
3. For a client requiring direct headers, use the vendor-documented `Authorization: Bearer <ACCESS_TOKEN>` and store the token securely.
4. Verify by searching official documentation. Do not create apps, test users, or webhooks as a connection check.

Mercado Pago’s current official tools table lists ten tools, including application_list (missing from the previous catalog). Application management and credentials tools are OAuth-only. Test-user balances and webhook configuration can mutate test/application state.

• search-documentation

  Search Mercado Pago Developers documentation by query and language.

  Parameters: query (required), language (required: es, en, pt)
  01
• quality_checklist

  Return the integration-quality checklist, required fields, and recommended best practices.

  02
• quality_evaluation

  Evaluate a production integration using payment_id or order_id.

  Parameters: payment_id (optional), order_id (optional; at least one required)
  03
• save_webhook

  Configure or update application webhook URLs and notification topics.

  Parameters: callback (optional), callback_sandbox (optional), topics (optional; defaults to payment)
  04
• notifications_history_diagnostics

  Diagnose webhook event history, delivery metrics, and failures.

  05
• create_test_user

  Create a test user for a country/site and profile, optionally with initial funds.

  Parameters: site_id (required), description (required), profile (required), amount (optional)
  06
• add_money_test_user

  Add test funds to a test user subject to country-specific amount limits.

  Parameters: test_user_id (required), amount (required)
  07
• get_credentials

  Return production and sandbox credentials for an application; OAuth only.

  Parameters: application_id (optional)
  08
• create_application

  Create a Mercado Pago application; OAuth only.

  Parameters: name (required), payment_solution (required), product (required), platform (optional), api_type (optional), description (optional), website_url (optional), redirect_url (optional)
  09
• application_list

  List or find applications in the authenticated Mercado Pago Developers account; OAuth only.

  10

• Application creation/listing and credential retrieval require OAuth. Test-user funding and webhook setup change service state; apply only to explicitly selected test users or applications.

• official complete tool reference

  Current official tools table lists ten tools and detailed parameters; it adds application_list to the previously stored nine.

• official product overview

  Official overview describes the MCP product lifecycle, supported tasks, and remote-client requirements.

Documentation checked 2026-10-28T14:06:33.000Z. Connection has not been runtime tested.