Mercado Pago MCP Server
OfficialRelated Servers
Alternatives to Mercado Pago MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA remote MCP server enabling AI agents to accept Pix, credit/debit cards, and boleto payments in Brazil via Mercado Pago, with payment status polling and no webhooks needed.MIT
- AlicenseCqualityCmaintenanceEnables Mercado Libre sellers to manage listings, catalog, stock, questions, and promotions through natural language using Codex and other MCP clients connected to the official API.41MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to accept payments in Chile using Mercado Pago, including cards, wallet, and bank transfers.MIT
- AlicenseNot gradedqualityBmaintenanceA remote MCP server that lets any AI agent accept payments in Argentina via Mercado Pago, supporting wallets, cards with cuotas, and cash.MIT

zuckpay-mcpofficial
AlicenseAqualityCmaintenanceOfficial MCP server for ZuckPay – create PIX, SPEI, and PayPal charges, and query transactions from your AI assistant.2023 npmMIT- FlicenseAqualityDmaintenanceMCP server that exposes the GestionIntegrantes REST API as tools, enabling authentication, management of personas, and user queries via natural language.10-
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.