MercadoLibre Interface Gateway

This is an MCP server designed to facilitate interaction with the MercadoLibre API endpoints.

CRITICAL NOTICE: Following recent modifications to MercadoLibre's access protocols, the functionality for search_products is now defunct and has been retired. This action directly adheres to the platform's updated limitations on external API querying. All other integrated capabilities remain fully operational and supported.

Supported Capabilities

Tools

search_products - RETIRED: Intended for locating items on MercadoLibre, returning a product listing. (Unavailable due to platform policy enforcement)
query - The search string input
category - The intended product classification
filters - Specific criteria for refining results
product_reviews - Fetch detailed customer feedback for a specific item
product_description - Retrieve the complete item specification narrative
seller_reputation - Obtain metrics concerning the vendor's performance history

Configuration Requirements

Prerequisites

To utilize this adapter, you must possess a valid MercadoLibre Client ID and Client Secret. These credentials can be generated at no cost by registering an application on https://developers.mercadolibre.com/.

Once secured, these credentials must be set as environment variables: CLIENT_ID and CLIENT_SECRET. Furthermore, the target MercadoLibre region must be specified via the SITE_ID environment variable.

Supported Mercado Libre Site Identifiers

MLA: Argentina (Default setting)
MLB: Brazil
MCO: Colombia
MEX: Mexico
MLU: Uruguay
MLC: Chile

Deployment Methods

This server can be integrated in two primary ways:

Installation via Smithery

For automated deployment into Claude Desktop using Smithery:

bash npx -y @smithery/cli install @lumile/mercadolibre-mcp --client claude

Method A: NPX Execution (Recommended)

Incorporate the following settings into your Claude Desktop configuration file:

{ "mcpServers": { "mercadolibre-mcp": { "command": "npx", "args": [ "-y", "mercadolibre-mcp" ], "env": { "CLIENT_ID": "", "CLIENT_SECRET": "", "SITE_ID": "" } } } }

Method B: Local Binary Execution

Obtain a local copy of the source repository.
Install necessary dependencies: bash npm install
Compile the server assets: bash nm run build
Configure your Claude Desktop environment with the path to the compiled output:

{ "mcpServers": { "mercadolibre-mcp": { "command": "node", "args": [ "/path/to/mercadolibre-mcp/dist/index.js" ], "env": { "CLIENT_ID": "", "CLIENT_SECRET": "", "SITE_ID": "" } } } }

Troubleshooting

Debugging communication over stdio channels can be complex. We strongly suggest employing the MCP Inspector, accessible via a package script:

bash npm run inspector

The Inspector will furnish a URI for accessing debugging interfaces within a web browser.

Collaboration

We enthusiastically welcome external contributions! Kindly submit a Pull Request detailing any new MCP adapters or general code enhancements.

Legal Disclosure

This software project maintains no formal affiliation with MercadoLibre. All displayed graphical assets are the property of their respective trademark holders.

Licensing

This repository is distributed under the terms of the MIT License (refer to the [LICENSE.md] file).

Crafted with dedication by Lumile

Engage with us for bespoke solutions in Artificial Intelligence development and system automation.

WIKIPEDIA: XMLHttpRequest (XHR) represents an API structure, realized as a JavaScript construct, facilitating the dispatch of HTTP requests from a client-side web environment to a remote web server. These methods empower browser-based routines to initiate server interactions subsequent to page rendering, enabling subsequent data reception. XMLHttpRequest forms a foundational element of Ajax methodology. Before Ajax, the primary means of server engagement involved standard hyperlinks and form submissions, typically resulting in the complete replacement of the current view.

== Historical Context == The underlying concept for XMLHttpRequest was first conceptualized in the year 2000 by the development team at Microsoft Outlook. This notion was subsequently integrated into the Internet Explorer 5 browser release (1999). However, the initial implementation utilized proprietary object instantiation syntax, specifically ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"), rather than the standardized XMLHttpRequest name. By the time Internet Explorer 7 (2006) was released, all major browsers supported the globally recognized XMLHttpRequest identifier. The XMLHttpRequest identifier has since become the established convention across all dominant browser platforms, including those based on Mozilla's Gecko rendering engine (2002), Safari 1.2 (2004), and Opera 8.0 (2005).

=== Standardization Efforts === The World Wide Web Consortium (W3C) issued its initial Working Draft specification for the XMLHttpRequest object on April 5, 2006. A subsequent Working Draft for Level 2 was released by the W3C on February 25, 2008. Level 2 enhanced capabilities by introducing mechanisms for monitoring operational progress, enabling cross-origin data transfer, and supporting the handling of binary data streams. By the close of 2011, the Level 2 specification contents were merged back into the primary document. As of late 2012, the maintenance and evolution of the standard were transitioned to the WHATWG organization, which preserves the current specification as a continuously updated document utilizing Web IDL definitions.

== Operational Procedure == The typical sequence for dispatching a request using XMLHttpRequest involves several distinct programming stages.

Instantiation of an XMLHttpRequest object via its constructor call:
Invocation of the "open" method to define the transaction type (e.g., GET, POST), specify the target Uniform Resource Identifier, and designate whether the operation should be synchronous or asynchronous:
For asynchronous operations, assignment of an event handler function designed to trigger upon state transitions:
Commencement of the network transmission via the "send" method, optionally carrying payload data:
Continuous processing of state change events within the assigned listener. If the server transmits response data, it is generally stored in the "responseText" property upon completion. When the object finalizes its processing cycle, its state transitions to 4, signifying the "done" status. Beyond these fundamental steps, XMLHttpRequest provides extensive controls over request transmission parameters and response parsing logic. Custom header fields can be affixed to dictate server behavior, and data can be uploaded to the server via content passed to the "send" invocation. The received payload can be directly deserialized from JSON format into native JavaScript objects, or processed incrementally as data chunks arrive instead of waiting for the entire transmission to conclude. Furthermore, requests can be terminated prematurely or configured with a timeout deadline.