/vendor/mercadolibre/AgentRouting.json or
/vendor/mercadolibre/AgentContext.json directly.
mercadolibre.com
Overview
Does mercadolibre.com support MCP?
Yes. mercadolibre.com has a confirmed MCP implementation. Developer tooling and API documentation assistant: tools to search Mercado Libre developer documentation, retrieve product identifiers, manage listings/orders/shipping for sellers, and query marketplace data; a distinct Mercado Pago sub-server (at https://mcp.mercadopago.com/mcp) exposes payment-integration tools separately from the marketplace server (at https://mcp.mercadolibre.com/mcp).
What agentic protocols does mercadolibre.com support?
As of 2026-06-30, mercadolibre.com has confirmed support for MCP.
Is mercadolibre.com's API publicly accessible or partner-gated?
Open.
Does mercadolibre.com explicitly prohibit automated access?
Yes. mercadolibre.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is mercadolibre.com agent-ready?
Partial. mercadolibre.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
Google's A2A launch partner lists name Atlassian, Box, Cohere, Intuit, PayPal, Salesforce, SAP, ServiceNow, and others — Mercado Libre does not appear. No vendor-specific evidence of A2A adoption, endpoint, or implementation was found for mercadolibre.com.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
The 60-organization contributor list published alongside Google's AP2 donation to the FIDO Alliance (May 2026) names Mastercard, American Express, PayPal, Adyen, Coinbase, Etsy, Forter, Intuit, JCB, Revolut, Salesforce, ServiceNow, UnionPay International, and Worldpay — but not MercadoLibre. No vendor-specific evidence was found of MercadoLibre adopting, piloting, or referencing AP2. This is not_found rather than confirmed_absent because MercadoLibre has not issued its own statement on the matter.
Developer tooling and API documentation assistant: tools to search Mercado Libre developer documentation, retrieve product identifiers, manage listings/orders/shipping for sellers, and query marketplace data; a distinct Mercado Pago sub-server (at https://mcp.mercadopago.com/mcp) exposes payment-integration tools separately from the marketplace server (at https://mcp.mercadolibre.com/mcp)
Two official, vendor-published MCP servers exist under the mercadolibre GitHub org: the Mercado Libre marketplace server at https://mcp.mercadolibre.com/mcp (documented at https://github.com/mercadolibre/mercadolibre-mcp-server and on the official developer portal) and a Mercado Pago payment server at https://mcp.mercadopago.com/mcp (documented at https://github.com/mercadolibre/mercadopago-mcp-server). Both use Streamable HTTP transport and Bearer token auth. The marketplace server was accepted into the official modelcontextprotocol/servers repository via PR #2341.
No evidence that Mercado Libre or its payments arm Mercado Pago appears in any MPP launch partner list or documentation. Named launch partners confirmed at launch include Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, Visa, Lightspark, and MultiversX — Mercado Libre is absent from all. No vendor-specific announcement, integration documentation, or developer reference linking mercadolibre.com to MPP was found.
No evidence that Mercado Libre has implemented or piloted NLWeb. Known early adopters of NLWeb (announced at Microsoft Build 2025) include Shopify, Tripadvisor, Chicago Public Media, and Hearst — all distinct from Mercado Libre. No mention of mercadolibre.com appears in any NLWeb partner or launch cohort coverage found.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence found that Mercado Libre has adopted or announced support for WebMCP. The protocol is in early developer preview (Chrome 146 Canary, gated behind a flag as of early 2026) with no public list of launch partners or early-adopter sites identified. Named early-adopter references in search results point to companies like Thumbtack and Amazon, not Mercado Libre.
No evidence found of Mercado Libre (mercadolibre.com) participating in x402 as a launch partner, foundation member, or early adopter. The x402 Foundation's confirmed members include Google, Microsoft, AWS, Visa, Mastercard, American Express, Cloudflare, Shopify, Stripe, Circle, Solana Foundation, and Polygon Labs — none of which is Mercado Libre. MercadoLibre is a major Latin American e-commerce and fintech platform with its own stablecoin infrastructure (Meli Dólar), making adoption theoretically plausible in the future, but no vendor-specific evidence was found.
No evidence found of an official MercadoLibre-published app on OpenAI's ChatGPT Apps platform (chatgpt.com/apps) built with the Apps SDK. Search results show: (1) a third-party Albato automation connector linking Mercado Libre to OpenAI's API, (2) multiple unofficial user-created GPTs on chatgpt.com (e.g., 'Mercado Libre PRO', 'MercadoLibre Asesor Virtual') that are community-built, not vendor-published, and (3) an OpenAI blog post about MercadoLibre's internal AI developer platform 'Verdi' using GPT-4o — an internal tooling integration, not a public ChatGPT App. No vendor-specific submission or listing in the ChatGPT app directory was found.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Direct HTTP fetches to mercadolibre.com for /llms.txt, /agents.md, /AGENTS.md, /.well-known/agent, and /.well-known/ai-plugin.json all timed out (DNS resolution failure from this environment), making passive checks impossible. Web searches found no third-party reports or vendor announcements of any self-declaration file published at mercadolibre.com. The most relevant Mercado Libre AI-related finding was an MCP integration for Mercado Pago developers and an internal AI platform (Verdi), neither of which is a self-declaration convention of this type.
Summary
Has agent interface: partial
Verify the two confirmed MCP servers (https://mcp.mercadolibre.com/mcp and https://mcp.mercadopago.com/mcp) are still live and responding correctly; confirm OAuth2 developer app registration flow remains self-serve at developers.mercadolibre.com; recheck for NLWeb, x402, and AP2 adoption given MercadoLibre's fintech scale and stablecoin infrastructure.
AgentContext
Five discrepancy categories were checked for mercadolibre.com: (1) pricing discrepancies — no evidence found of hidden fees or checkout price divergence from listed prices; (2) availability discrepancies — no platform-level ghost inventory or bait-and-switch issues documented, though third-party seller fraud exists on all large marketplaces; (3) identity/merchant-of-record ambiguity — Mercado Libre's marketplace structure and dispute mediation role are disclosed in published terms and developer documentation, with no regulatory findings of systematic buyer deception about the legal counterparty; (4) policy discrepancies — individual consumer complaints (e.g., identity verification blocking refunds) were found on Trustpilot but no regulatory enforcement or class-action findings confirming a systemic gap between stated and enforced cancellation or return policies; (5) undisclosed transactional constraints — published marketplace terms for Mexico and Brazil openly describe payment method restrictions, and no independently verified mid-transaction capability failures were documented. All five categories returned no finding meeting the inclusion bar. No search scans were blocked or missing, though results in the availability category were partially dominated by unrelated marketplace fraud content, limiting depth of coverage there.