Avito MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_PATH | No | Alternative environment variable for the path to a specific Chrome/Chromium executable. | |
| AVITO_CDP_URL | No | CDP connection address. | http://127.0.0.1:9222 |
| AVITO_CDP_PORT | No | Debugging port used by the npm run cdp script. | 9222 |
| AVITO_DATA_DIR | No | Path to the directory used to store the Avito session data. | ./avito-data |
| AVITO_HEADLESS | No | Force headless mode on (true) or off (false). By default, desktop browsers run in a window off-screen, and Linux servers without a display run headless. | |
| AVITO_NO_SANDBOX | No | Force enable the --no-sandbox flag. Automatically enabled on Linux as root or in Docker. | |
| AVITO_CHROME_PATH | No | Path to a specific Chrome/Chromium executable if installed in a non-standard location. | |
| PUPPETEER_EXECUTABLE_PATH | No | Alternative environment variable for the path to a specific Chrome/Chromium executable. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| avito_searchB | Search for listings on Avito by query, location, price range and sort order. |
| avito_get_item_detailsA | Get full details of an Avito listing: title, price, description, seller rating/reviews, parameters, delivery status and messaging capability. |
| avito_send_messageA | Send a message to a seller on Avito to negotiate or ask questions. Requires prior login via npm run login. |
| avito_list_chatsA | List recent chats from the user's Avito messenger. Requires prior login. |
| avito_get_chat_historyB | Read message history in an active Avito chat to check seller responses. |
| avito_download_imagesA | Download photos from an Avito listing to local disk for visual AI inspection. Returns array of local file paths and image URLs. |
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 6 tools
Each tool targets a distinct resource+action: search (query listings), get_item_details (single listing), send_message (outbound messaging), list_chats (conversation index), get_chat_history (messages within a chat), download_images (media retrieval). The messaging trio is cleanly separated by scope (send vs. list vs. read), and download_images has no overlap with anything else.
All six tools use the same avito_ prefix followed by a snake_case verb_noun pattern (get_item_details, send_message, list_chats, get_chat_history, download_images). The single bare verb (avito_search) is still read as a domain-scoped action and is consistent with the rest of the set.
Six focused tools cover a marketplace browse-and-message workflow without redundancy; every tool maps to a real step in the search → inspect → contact → follow-up loop. Nothing feels padded or missing from a count perspective.
The core lifecycle (search, listing details, image inspection, send message, list chats, read history) is covered with no dead ends for the main workflow. Minor gaps remain: authentication is pushed to an external 'npm run login' step with no tool to trigger or verify login state, and there is no favorites/watchlist or own-listings retrieval.