demo-mercadopago

This MCP server exposes tools to help you integrate Mercado Pago into your applications. The repository identifies a primary tool called search_documentation, which lets you query Mercado Pago’s developer documentation by language (es, pt), term, and country site (MLA, MLB, MLM, MPE, etc.). You can invoke this tool by configuring your MCP client to call the mercadopago server and selecting the search_documentation tool with the required parameters. The tool returns structured search results with links to relevant Mercado Pago guides and documentation to accelerate integration work. In your IDE or MCP client, you enable debugging if needed to see the request/response payloads and verify that environment credentials are being used correctly.

Prerequisites:

• Node.js installed on your machine
• npm installed (enabled via Node.js)
• Mercado Pago API credentials (CLIENT_ID and CLIENT_SECRET)

Installation steps:

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. Obtain Mercado Pago API credentials

   • CLIENT_ID: Your Mercado Pago application ID
   • CLIENT_SECRET: Your Mercado Pago secret key
   • You can also set DEBUG=true in the environment to enable verbose logging

4. Run or configure the MCP server in your IDE

   • For IDEs like Claude Desktop or Windsurf, configure the server with:

     { "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 } } } }

5. Start the server locally (example)

   • Ensure environment variables are set, then run the Node.js entrypoint if you prefer direct execution: node build/index.js

Tips and common issues:

• Ensure your Mercado Pago credentials are kept secret; do not commit them to source control.
• If you encounter connection or authentication errors, verify that CLIENT_ID and CLIENT_SECRET are correctly set in the environment where the server runs.
• The DEBUG environment variable is optional but helpful during setup to get verbose logs.
• Build artifacts are expected under build/index.js; if you modify source, re-run npm run build if your setup requires it.
• The MCP server configuration assumes a single mercadopago server entry named mercadopago; you can adjust the server name in the mcp_config accordingly.
• When using with IDEs, ensure the path in args points to the actual built entry point in your environment.