avito-mcp-ru
Related Servers
Alternatives to avito-mcp-ru
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceYandex Market Partner API in your AI assistant: orders and returns, products and cards, prices and tariffs, reports, reviews and chats. 165 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.2626 PyPI2MIT
- AlicenseAqualityAmaintenanceOzon Seller API in your AI assistant: products, FBS and FBO orders, prices, stocks, finance and reviews. 441 methods live in a YAML catalog the server executes, the agent searches it in plain language and calls a method through three generic tools, and every method carries an access class so writes and irreversible calls ask for confirmation.2541 PyPI3MIT
- AlicenseAqualityAmaintenanceWildberries seller API in your AI assistant: sales and stocks, product cards, prices and promotions, financial reports and reviews. 307 methods across all 17 Wildberries hosts 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.2531 PyPI2MIT
- AlicenseAqualityAmaintenanceUniversal MCP server for the Avito API (Russia's largest classifieds marketplace), built for autonomous AI agents to operate an account hands-free — 145 tools across 18 domains (listings, messenger, orders, delivery, promotion, autoload, reviews, analytics). Safe-by-default: dry-run, idempotency, structured errors, confirmation flow.144264 npm18MIT
- AlicenseAqualityAmaintenanceVK API for AI assistants: wall posts, communities, messages, market items, ads and stats. 373 methods in one catalog, each with a read/write/destructive safety class; the agent searches methods in plain language instead of receiving 373 tools.1857 PyPI1MIT
- AlicenseAqualityAmaintenanceMCP server that enables natural-language interaction with the Avito Ads advertising API, including campaign, ad group, and creative management, statistics retrieval, fund transfers, and ORD paperwork filing.26110 npmMIT
TDQS
Scored across 30 tools
The catalog navigation tools (avito_list_sections, avito_get_section, avito_search_methods, avito_describe_method) overlap somewhat in purpose, but descriptions clarify their roles. More problematically, read/write/delete execution tools come in both catalog-based (avito_call_method/avito_write_method/avito_delete_method) and raw-path (avito_get_raw/avito_write_raw/avito_delete_raw) variants, creating two parallel execution surfaces that could be confused.
Most tools follow an avito_verb_noun pattern (avito_list_sections, avito_get_items, avito_update_price), but there are inconsistencies: avito_map, avito_whoami, avito_fetch_all, and avito_set_key break the verb_noun convention. The call/write/delete_method vs get/write/delete_raw naming is also not parallel (call vs get), which undermines predictability.
30 tools is heavy for a marketplace MCP server, and many are meta-tools (sections, methods, raw execution, cabinets) rather than domain operations. The six raw/catalog execution variants could be consolidated, while domain-specific getters are duplicated by generic call_method. It feels over-engineered and over-scoped.
Core read operations are covered (items, orders, stocks, stats, reviews, chats, balance) and write operations exist for price and stock. However, the domain lacks common lifecycle operations like creating/editing listings, responding to reviews, messaging buyers, or acting on orders, which a marketplace seller would expect.