Mercado Pago MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MERCADOPAGO_ENVIRONMENT | No | Environment to use: 'sandbox' or 'production'. Defaults to 'sandbox'. | sandbox |
| MERCADOPAGO_ACCESS_TOKEN | Yes | Your Mercado Pago access token. Starts with 'TEST-' for sandbox or 'APP_USR-' for production. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_paymentC | Create a new payment in Mercado Pago |
| get_paymentC | Get payment details by ID |
| search_paymentsC | Search for payments with filters |
| cancel_paymentB | Cancel a pending payment |
| create_refundC | Create a refund for a payment |
| create_customerB | Create a new customer |
| get_customerB | Get customer details |
| search_customersC | Search for customers |
| create_payment_linkC | Create a payment link (checkout preference) |
| simulate_webhookA | Simulate a webhook notification for testing |
| create_pix_paymentB | Create a PIX payment with QR code |
| create_subscriptionC | Create a recurring subscription |
| get_subscriptionC | Get subscription details |
| update_subscriptionB | Update subscription (pause, resume, modify) |
| create_split_paymentC | Create a marketplace split payment |
| save_cardB | Save a card for future payments |
| list_saved_cardsC | List customer's saved cards |
| get_payment_methodsA | Get available payment methods for your country |
| batch_create_paymentsC | Create multiple payments in batch |
| monitor_payment_statusC | Monitor payment status changes in real-time |
| retry_failed_paymentC | Automatically retry a failed payment with smart logic |
| get_analytics_dashboardC | Get comprehensive payment analytics and metrics |
| detect_fraud_riskB | Analyze payment for fraud risk indicators |
| schedule_payment_reminderC | Schedule automatic payment reminders |
| export_to_accountingB | Export payment data to accounting software format |
| calculate_taxesA | Calculate taxes for a payment based on region |
| generate_reportsC | Generate payment reports |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 27 tools
Most tools target distinct resource-action pairs, but there is some potential confusion between general payment creation (create_payment) and specific variants (create_pix_payment, create_split_payment, batch_create_payments) as well as among reporting/analytics tools. Descriptions mitigate most ambiguity.
All tools use snake_case and mostly follow a verb_noun pattern, but a few names deviate from the standard (batch_create_payments, monitor_payment_status, schedule_payment_reminder) and mix verb forms. The convention is more consistent than not.
With 27 tools, the server exceeds the threshold for a well-scoped toolset. While Mercado Pago is a complex platform, the number is high and could overwhelm agents, and several tools could be consolidated (e.g., payment creation variants, reporting tools).
The toolset covers the core payment lifecycle (create, read, search, cancel, refund), customer management, subscriptions, cards, and adds analytics, fraud, and reporting. Minor gaps exist like no customer update/delete, no subscription cancellation, and no card removal, but these are not critical for basic workflows.