SkillFoxx

avito-mcp with multiple accounts

avito-mcp

An Avito API MCP with support for up to nine accounts, an honest list of what the API cannot change, and a Railway deployment

  • 1 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • Can send messages on your behalf and change listing prices
  • The server access secret is embedded in the connector URL
All reasons and checks
Russian stack

irikrafikov-ai/avito-mcpAuthor:irikrafikov-ai

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/irikrafikov-ai-avito-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Can send messages on your behalf and change listing prices
  • The server access secret is embedded in the connector URL

This is third-party code. Review the repository files before installing.

What it does

The server gives Claude access to Avito listings, statistics, messaging and autoload data through the official API. It supports from one to nine accounts at once: the second and later ones are set with _2 and higher suffixed variables, or a single AVITO_ACCOUNTS variable with a JSON array. The avito_accounts tool lists connected accounts, and the rest gain an account parameter. Read tools: whoami, balance, listing list, listing card and statistics, chat list, chat messages, autoload reports. Write tools: sending a message, updating price, marking as read. A fallback avito_request calls any API method directly. The README separately clarifies that the REST API cannot change a listing's title, description, photos or attributes, only its price, with everything else going through an XML or CSV autoload feed. The server deploys to Railway and exposes an MCP endpoint at an address with the secret embedded in the URL itself.

Who it is for. For sellers with several Avito accounts who need a single MCP server with switching between them and an honest description of what the API can and cannot change.

Good fit when

  • You run several Avito accounts and want to work with them from one server
  • You need autoload reports and clarity on which fields can only be edited via a feed
  • You need a Railway deployment with a public domain, not just a local run

Not a fit when

  • You need to change a listing's title, description, photos or attributes through the API: neither Avito nor the server can do this
  • You do not want a secret embedded directly in the connector URL for a cloud deployment

Example request

Show the balance and latest autoload reports for the dolina account

MCP

Transport
http
Authentication
API key

Environment variables

AVITO_CLIENT_ID required, secret
The client_id from the Avito developer account.
AVITO_CLIENT_SECRET required, secret
The client_secret from the same place.
MCP_SECRET required, secret
A random string that becomes part of the connector URL.

Limitations

Through Avito's REST API only the listing price can be changed; every other field must go through an XML or CSV autoload feed. With a Railway cloud deployment, the MCP_SECRET becomes part of the connector URL, so that URL must be kept as carefully as a password. It needs AVITO_CLIENT_ID and AVITO_CLIENT_SECRET from the Avito developer account for each connected account.

How to disable. Remove the custom connector with the server URL in Claude's settings and stop or delete the Railway service.

FAQ

Can I change a listing's photo or description?

No, Avito's API does not allow it; the only field editable via REST is price, everything else goes through the autoload feed.

How do I work with multiple accounts?

Set variables with _2, _3 and so on suffixes, or one AVITO_ACCOUNTS variable with a JSON array; the avito_accounts tool shows the list.

Discussion

No questions or reviews yet.

All Avito tools
Russian stack

An MCP server for an Avito seller account: buyer chats, listings, stats, promotion and orders, with a read-only mode

MCP serverBroad access26
Russian stack

A compact MCP for Avito Messenger and items with user_id auto-detection, SSL bypass for corporate proxies, and an interactive deploy.sh

MCP serverBroad access

Avito Ads MCP

A1 Авито Реклама MCP

Russian stack

An MCP for the Avito Ads account: campaigns, stats, group budget and bid, balance, access and ORD documents, 25 tools

MCP serverBroad access1
Russian stack

MCP server in Go for the Avito Business API: profile, own listings, price changes, chats and sending messages to buyers

MCP serverBroad access
Russian stack

An MCP server for Avito through a running Chrome over CDP: search, listings, photos, messenger, Delivery orders and closing your own listings

MCP serverBroad access
Russian stack

A single-marketplace distribution of the marketplaces-mcp-ru core just for Avito: 64 API methods via a method catalog instead of a hundred separate tools

MCP serverBroad access4

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialAuthenticationRepository starsMain difference
avito-mcp with multiple accounts (this card)noAPI key1
avito-mcpnoAPI key26chats, listings and seller orders
Avito login MCP server over the mobile APInonot required0AI agent
Avito MCP for Messenger and ItemsnoOAuth0a compact server for Avito Messenger and listings

README in short

The README gives a table of environment variables marked as required or optional, explains the multi-account scheme via suffixes or a single AVITO_ACCOUNTS variable, an MCP_SECRET generation command, a local run and a Railway deployment with variables and a public domain, a list of read and write tools, and a separate section on what the API cannot do.

README badge

Report a problem