mercadolivre-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ML_CLIENT_ID | Yes | The client id of your Mercado Livre application | |
| ML_SECRETS_DIR | No | Optionally set this to choose where the token is stored (default: ~/.config/mercadolivre-mcp) | |
| ML_REDIRECT_URI | Yes | The redirect URI configured for your Mercado Livre application | |
| ML_CLIENT_SECRET | Yes | The client secret of your Mercado Livre application |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ml_get_accountA | Read-only. Return the authenticated seller's id, nickname, reputation level, power seller status, transaction counts and metrics. |
| ml_list_itemsA | Read-only. List the seller's items by status with a short summary of each (price, stock, sales, pictures, variations). Paginated with limit and offset. |
| ml_get_itemA | Read-only. Return one item with its summary, attributes and plain-text description (null when the item has no description). |
| ml_get_item_visitsB | Read-only. Return daily visit counts for an item over the last N days. |
| ml_list_questionsA | Read-only. List buyer questions on the seller's items, filtered by status (UNANSWERED or ANSWERED) and optionally by item. Paginated with limit and offset. |
| ml_list_ordersA | Read-only. List the seller's orders from the last N days, newest first, one row per order item (price, quantity, sale fee). Paginated by order with limit and offset. |
| ml_api_getA | Read-only. Send a GET request to a Mercado Livre API path and return the JSON response, for example /categories/MLB1234. Only paths on the API host are allowed. |
| ml_update_itemA | Change fields of one of your Mercado Livre items (price, stock, title, status, pictures, variations, ...). Nothing is changed unless confirm=true. Call it without confirm first to get a preview (before, after and the exact request), show that preview to the user, and call again with confirm=true only after their explicit approval. Partial |
| ml_upload_pictureA | Upload a local image to Mercado Livre and return its picture id. Only real JPEG, PNG or WEBP files up to 10 MB are accepted, given by absolute path; anything else is refused. An uploaded picture gets a public URL on Mercado Livre's CDN, even before it is attached to an item with ml_update_item. Nothing is uploaded unless confirm=true. Call it without confirm first to get a preview (file, type and size), show that preview to the user, and call again with confirm=true only after their explicit approval. |
| ml_answer_questionA | Answer a buyer question on one of your Mercado Livre listings. The answer is public on the listing. Nothing is sent unless confirm=true. Call it without confirm first to get a preview (the question and the exact request), show that preview to the user, and call again with confirm=true only after their explicit approval. |
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 10 tools
Most tools target clearly distinct resources and actions (account, items, visits, questions, orders), with write tools distinguished by their mandatory confirm-preview flow. The only real overlap is ml_api_get, a generic escape hatch that can retrieve anything the specific getters return, but its description makes the raw-API nature explicit.
Names share a consistent ml_ prefix and mostly follow verb_noun (get_account, list_items, get_item, list_questions, update_item, upload_picture, answer_question). The lone deviation is ml_api_get, which breaks the verb_noun reading slightly but is still clear.
Ten tools is well-scoped for a seller-management server, covering account, items, visits, questions, orders, and the key write operations without redundancy. Each tool earns its place.
Read coverage is strong (account, items, visits, questions, orders) and item update, picture upload, and question answering are supported. However, there is no create_item or delete_item, so an agent cannot publish or remove listings through the dedicated surface and must fall back to the generic ml_api_get.