Skip to main content
Glama
mercadolibre

Mercado Pago MCP Server

Official
by mercadolibre
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Demo Mercado Pago MCP Server

A Model Context Protocol server that provides tools for integrating Mercado Pago into your applications.

Installation & Setup

  1. Clone the repository:

    git clone https://github.com/mercadolibre/demo-mercadopago-mcp-server.git
cd demo-mercadopago-mcp-server

  2. Install dependencies:

    npm install

  3. Get Mercado Pago API credentials

    You'll need to provide valid Mercado Pago API credentials through the environment variables:

  4. Configure MCP Server in your IDE

    To use with Claude Desktop or other MCP-compatible applications (including Windsurf, Cursor, Cline, etc), add the server configuration to your settings:

    {
  "mcpServers": {
    "mercadopago": {
      "command": "node",
      "args": ["/path/to/demo-mercadopago-mcp-server/build/index.js"],
      "env": {
        "CLIENT_ID": "your-mercadopago-client-id",
        "CLIENT_SECRET": "your-mercadopago-client-secret",
        "DEBUG": "true"  // Optional: Enable debug logging
      }
    }
  }
}

Related MCP server: app.wishpool/argentina-payments-mcp

Available Tools

search_documentation

Search through Mercado Pago's documentation.

Parameters

  • language (string, required)

    • Documentation language

    • Options: "es" (Spanish), "pt" (Portuguese)

  • query (string, required)

    • Search term to find in documentation

  • siteId (string, required)

    • Country site identifier

    • Options: "MLB" (Brazil), "MLA" (Argentina), "MLM" (Mexico), "MLU" (Uruguay), "MLC" (Chile), "MCO" (Colombia), "MPE" (Peru)

  • limit (number, optional)

    • Maximum number of results to return

    • Default: 10

    • Range: 1-100

Example Request

<use_mcp_tool>
<server_name>mercadopago</server_name>
<tool_name>search_documentation</tool_name>
<arguments>
{
  "language": "es",
  "query": "checkout pro",
  "siteId": "MLA",
  "limit": 3
}
</arguments>
</use_mcp_tool>

Example response:

# Search Results for "checkout pro"
Showing 3 of 8 results

## Checkout Pro
Checkout Pro es una solución que permite a tus clientes realizar pagos de forma segura...

🔗 [Read more](https://www.mercadopago.com.ar/developers/es/guides/checkout-pro/introduction)

Score: 0.95

---

## Integrar Checkout Pro
Aprende a integrar Checkout Pro en tu sitio web para comenzar a recibir pagos...

🔗 [Read more](https://www.mercadopago.com.ar/developers/es/guides/checkout-pro/integration)

Score: 0.85

Development Guide

Building

Install dependencies:

npm install

Build the server:

npm run build

Watch mode for development:

npm run watch

Running

Configure environment variables:

export CLIENT_ID=your_mercadopago_client_id
export CLIENT_SECRET=your_mercadopago_client_secret
export DEBUG=true  # Optional: Enable debug logging

Start the server:

npm start

Run with inspector for testing:

npm run inspector

Available Tools

1 tool
search_documentationC

Search Mercado Pago documentation

ParametersJSON Schema
NameRequiredDescriptionDefault
languageYesLanguage of the documentation (es: Spanish, pt: Portuguese)
queryYesSearch query
siteIdYesSite ID for documentation
limitNoMaximum number of results to return (default: 10)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't mention whether this is a read-only operation, potential rate limits, authentication requirements, error conditions, or what the search results look like. 'Search' implies read-only, but this isn't explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with zero wasted words. It's appropriately sized for a simple search tool and front-loads the core functionality effectively.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with 4 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the search returns, how results are ranked, pagination behavior, or error handling. The schema covers parameters well, but the overall context for tool usage is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all parameters. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline for high coverage but not providing extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Search') and resource ('Mercado Pago documentation'), making the purpose immediately understandable. It doesn't need to differentiate from siblings since none exist, but it could be more specific about what kind of search this performs (e.g., full-text, title-only).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or typical use cases. The description is a simple statement of function without context about appropriate scenarios or limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as searching documentation, making it impossible to confuse with other tools.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (search_documentation), and with only one tool, consistency is inherently perfect as there are no other names to compare against.

Tool Count2/5

A single tool is too few for a server named 'Mercado Pago MCP Server', which implies a broader scope related to payment processing. This minimal toolset feels thin and inadequate for the apparent domain, limiting functionality to just documentation search.

Completeness1/5

The tool surface is severely incomplete for a payment processing domain. There are no tools for core operations like creating payments, checking transaction status, managing customers, or handling refunds, leaving significant gaps that will cause agent failures in typical workflows.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mercadolibre/demo-mercadopago-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server