About Mercado Livre - MCP Server
Mercado Livre - MCP Server retrieves product data through the Mercado Livre API. It is intended for MCP client workflows that need product details such as prices and availability, and uses layered architecture with Zod input validation.
Key features
- 01Fetch basic product information
- 02Validate inputs with Zod
- 03Request data through the Mercado Livre API
- 04Organise services in layers
Use cases
- 01Look up Mercado Livre product details
- 02Retrieve product prices and availability in an MCP client
MCP support
The MCP server exposes a `get-produtos` tool over stdio to retrieve product information from Mercado Livre.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMercado Livre - MCP Server
This project is part of the Model Context Protocol (MCP) ecosystem and provides tools for integrating with external sources and managing specific domain models. It is designed to demonstrate how to build an MCP server that scrapes products from Mercado Livre, with strong data validation to ensure reliability.
| An integration that enables MCP tools to scrape product data, such as prices and availability, directly from Mercado Livre. |
|
Table of Contents
- Features
- Architecture
- Installation
- MCP Server Configuration in VSCode
- MCP Server Output in VSCode
- Contribution
- License
Features
- get-produtos: Fetch basic product information.
- Input validation using Zod.
- Integration with the Mercado Livre API using
fetch(infrastructure layer).
Architecture
The project follows a layered architecture inspired by Domain-Driven Design (DDD) patterns:
-
Domain (
src/domain): Defines interfaces and types that represent data structures (e.g.,Mercado Livre). -
Infrastructure (
src/infrastructure): Implements external services, such asMercadoLivreApiService, responsible for making HTTP calls to the Mercado Livre API. -
Application (
src/application): Contains business logic inMercadoLivreService, which processes and formats data from the infrastructure. -
Interface (
src/interface): Includes controllers (MercadoLivreToolsController) that register tools in the MCP server, define validation schemas, and return results. -
Entry Point (
src/main.ts): Initializes theMcpServer, configures the transport (StdioServerTransport), instantiates services and controllers, and starts listening on stdio.
The folder structure is as follows:
src/
├── domain/
│ └── models/ # Domain interfaces
├── infrastructure/
│ └── services/ # External API implementations (Mercado Livre)
├── application/
│ └── services/ # Business logic and data formatting
├── interface/
│ └── controllers/ # MCP tool registration and validation
└── main.ts # Server entry point
build/ # Compiled JavaScript code
.vscode/ # Contains the mcp.json file, MCP Server config
Installation
git clone [email protected]:newerton/mcp-mercado-livre.git
cd mcp-mercado-livre
npm install
npm run build
MCP Server Configuration in VSCode
- Press
Ctrl+Shift+Pand select "MCP: List Servers" - Select "products" and then "Start Server"
MCP Server Output in VSCode
- Press
Ctrl+Shift+Pand select "MCP: List Servers" - Select "products" and then "Show Output"
Contribution
Pull requests are welcome! Feel free to open issues and discuss improvements.
License
This project is licensed under the MIT license - see the LICENSE file for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.