Mercado Pago MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | true |
| CLIENT_ID | Yes | Your Mercado Pago application ID from the Mercado Pago Developer Dashboard | |
| CLIENT_SECRET | Yes | Your Mercado Pago secret key from the Mercado Pago Developer Dashboard |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documentationC | Search Mercado Pago documentation |
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 1 tool
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.
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.
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.
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.