Avito MCP Server
Related Servers
Alternatives to Avito MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables local-first, read-only interaction with Avito through your own authenticated Chrome session, without sharing credentials with the MCP client. Provides tools for searching listings, viewing your listings, favorites, chats, and messages.22MIT
- AlicenseBqualityBmaintenanceEnables an LLM to control a separate Chrome session on Avito for searching and parsing listings, reading account and Pro dashboards/statistics, switching profiles, and editing forms. Requires explicit confirmation for irreversible actions.183MIT
- AlicenseAqualityAmaintenanceEnables AI clients to search Avito listings by city, price, and sort order, inspect complete listing cards, and review seller ratings and recent feedback locally in read-only mode.1050MIT
- AlicenseAqualityBmaintenanceEnables searching cian.ru apartment listings through a live authorized browser session, including login/session management, filtered offer search, and detailed offer cards with price history.41MIT
- AlicenseAqualityCmaintenanceEnables read-only buyer-side searches of live Avito listings for used PC components, inspection of full listing cards, and side-by-side comparison of exact offers, defaulting to Yekaterinburg without an Avito account or API key.5MIT
- AlicenseAqualityAmaintenanceAvito business API in your AI assistant: listings and statistics, buyer messenger, orders and Avito Delivery, bulk upload, promotion and reviews. 64 methods live in a YAML catalog the server executes, the agent searches it in plain language, and every method carries an access class so writes and irreversible calls ask for confirmation.3036 PyPI3MIT
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.