avito-mcp-ru
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
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- 22 methods write data, including messenger replies and stock changes
- Two methods are irreversible, and OAuth2 keys for several accounts are stored locally
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/avito-mcp-ruDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
This entry is high risk, so there is no one-click install. Review the code and add the config by hand.
Run in a terminal
claude mcp add --transport stdio --env 'AVITO_CLIENT_ID=<your AVITO_CLIENT_ID>' --env 'AVITO_CLIENT_SECRET=<your AVITO_CLIENT_SECRET>' avito-mcp-ru -- uvx avito-mcp-ru==0.6.0Or add to the file .mcp.json, in the project
{
"mcpServers": {
"avito-mcp-ru": {
"command": "uvx",
"args": [
"avito-mcp-ru==0.6.0"
],
"env": {
"AVITO_CLIENT_ID": "<your AVITO_CLIENT_ID>",
"AVITO_CLIENT_SECRET": "<your AVITO_CLIENT_SECRET>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"avito-mcp-ru": {
"command": "uvx",
"args": [
"avito-mcp-ru==0.6.0"
],
"env": {
"AVITO_CLIENT_ID": "<your AVITO_CLIENT_ID>",
"AVITO_CLIENT_SECRET": "<your AVITO_CLIENT_SECRET>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
code --add-mcp '{"name":"avito-mcp-ru","type":"stdio","command":"uvx","args":["avito-mcp-ru==0.6.0"],"env":{"AVITO_CLIENT_ID":"<your AVITO_CLIENT_ID>","AVITO_CLIENT_SECRET":"<your AVITO_CLIENT_SECRET>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"avito-mcp-ru": {
"type": "stdio",
"command": "uvx",
"args": [
"avito-mcp-ru==0.6.0"
],
"env": {
"AVITO_CLIENT_ID": "<your AVITO_CLIENT_ID>",
"AVITO_CLIENT_SECRET": "<your AVITO_CLIENT_SECRET>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
codex mcp add avito-mcp-ru --env 'AVITO_CLIENT_ID=<your AVITO_CLIENT_ID>' --env 'AVITO_CLIENT_SECRET=<your AVITO_CLIENT_SECRET>' -- uvx avito-mcp-ru==0.6.0Or add to the file ~/.codex/config.toml, for all projects
[mcp_servers.avito-mcp-ru]
command = "uvx"
args = ["avito-mcp-ru==0.6.0"]
env = { AVITO_CLIENT_ID = "<your AVITO_CLIENT_ID>", AVITO_CLIENT_SECRET = "<your AVITO_CLIENT_SECRET>" }If the file already exists, append the block to the end.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run in a terminal
gemini mcp add -s user -e 'AVITO_CLIENT_ID=<your AVITO_CLIENT_ID>' -e 'AVITO_CLIENT_SECRET=<your AVITO_CLIENT_SECRET>' avito-mcp-ru uvx avito-mcp-ru==0.6.0Or add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"avito-mcp-ru": {
"command": "uvx",
"args": [
"avito-mcp-ru==0.6.0"
],
"env": {
"AVITO_CLIENT_ID": "<your AVITO_CLIENT_ID>",
"AVITO_CLIENT_SECRET": "<your AVITO_CLIENT_SECRET>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"avito-mcp-ru": {
"command": "uvx",
"args": [
"avito-mcp-ru==0.6.0"
],
"env": {
"AVITO_CLIENT_ID": "<your AVITO_CLIENT_ID>",
"AVITO_CLIENT_SECRET": "<your AVITO_CLIENT_SECRET>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"avito-mcp-ru": {
"command": "uvx",
"args": [
"avito-mcp-ru==0.6.0"
],
"env": {
"AVITO_CLIENT_ID": "<your AVITO_CLIENT_ID>",
"AVITO_CLIENT_SECRET": "<your AVITO_CLIENT_SECRET>"
}
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"avito-mcp-ru": {
"command": "uvx",
"args": [
"avito-mcp-ru==0.6.0"
],
"env": {
"AVITO_CLIENT_ID": "<your AVITO_CLIENT_ID>",
"AVITO_CLIENT_SECRET": "<your AVITO_CLIENT_SECRET>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"avito-mcp-ru": {
"type": "local",
"command": [
"uvx",
"avito-mcp-ru==0.6.0"
],
"environment": {
"AVITO_CLIENT_ID": "<your AVITO_CLIENT_ID>",
"AVITO_CLIENT_SECRET": "<your AVITO_CLIENT_SECRET>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"avito-mcp-ru": {
"command": "uvx",
"args": [
"avito-mcp-ru==0.6.0"
],
"env": {
"AVITO_CLIENT_ID": "<your AVITO_CLIENT_ID>",
"AVITO_CLIENT_SECRET": "<your AVITO_CLIENT_SECRET>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"avito-mcp-ru": {
"command": "uvx",
"args": [
"avito-mcp-ru==0.6.0"
],
"env": {
"AVITO_CLIENT_ID": "<your AVITO_CLIENT_ID>",
"AVITO_CLIENT_SECRET": "<your AVITO_CLIENT_SECRET>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
AVITO_CLIENT_IDsecret, required- client_id из раздела Для бизнеса → Интеграции → API.
AVITO_CLIENT_SECRETsecret, required- client_secret оттуда же, меняется на токен по OAuth2.
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Run the server with uvx --from git+https://github.com/ilyautov/avito-mcp-ru avito-mcp-ru (shorter after release: uvx avito-mcp-ru), set AVITO_CLIENT_ID and AVITO_CLIENT_SECRET from the Для бизнеса, Интеграции, API section on avito.ru in your client config, or ask the agent to set everything up itself with npx skills add ilyautov/avito-mcp-ru.
Other ways from the author
uvx --from git+https://github.com/ilyautov/avito-mcp-ru avito-mcp-ruBefore the first PyPI release; after release the command is shorter: uvx avito-mcp-ru.
This is third-party code. Review the repository files before installing.
What it does
The server runs a single MCP for the official Avito API and nothing else; it gets its core and method catalog as a dependency from the same author's marketplaces-mcp-ru project. Instead of a separate tool per method, the agent searches a catalog of 64 methods (40 reads, 22 writes, 2 irreversible) in Russian or English, grouped by messenger, autoload, orders and Avito delivery, listings and statistics, promotion, ratings and reviews, balance, and stock. An OAuth2 client_id and client_secret pair is exchanged for a token automatically, and keys for several accounts can be stored in ~/.marketplace-mcp/cabinets.json with 600 permissions and switched right from the chat.
Who it is for. For sellers who work only with Avito and do not want to install a package with all four marketplaces at once.
Good fit when
- You need Avito only, without Wildberries, Ozon and Yandex Market in the same server
- You need to work with several Avito accounts and switch between them
- You need both reading statistics and operations like replying in the messenger or updating stock
Not a fit when
- You need several marketplaces at once: it is simpler to install the same author's marketplaces-mcp-ru
- The catalog has not been verified on real accounts yet: the README is honest that no live run has been done
Example request
Show my Avito listing statistics for the week and collect unread messenger conversationsLimitations
The method catalog is built from official Avito documentation, but according to the author no live run on real accounts has been done yet, so field name mismatches are possible and fixed via describe_method and avito_get_raw. Access to API sections, including messenger and Avito Delivery, is granted by Avito on request and differs between accounts. The OAuth2 token has a limited lifetime and must be refreshed manually if called outside the server.
How to disable. Remove the avito server from your MCP client config and delete the ~/.marketplace-mcp/cabinets.json file with saved accounts.
MCP
- Transport
- stdio
- Authentication
- OAuth
| Environment variables | |
|---|---|
| AVITO_CLIENT_ID required, secret | The client_id from the Для бизнеса, Интеграции, API section on avito.ru. |
| AVITO_CLIENT_SECRET required, secret | The client_secret from the same section, exchanged for an access token via OAuth2. |
Security check
- 22 methods write data, including messenger replies and stock changes
- Two methods are irreversible, and OAuth2 keys for several accounts are stored locally
README in short
The README gives three install methods (uvx from git, uvx after a PyPI release, self-install via a skill), explains getting a client_id and client_secret pair on avito.ru and their exchange for a token, a method map table by topic with read, write and irreversible operation counts, example chat questions, a common 401 and 403 errors section, and an explicit comparison with the same author's marketplaces-mcp-ru package.
FAQ
How is this different from marketplaces-mcp-ru?
Only in what it installs: this package runs a single Avito server, while marketplaces-mcp-ru installs all four marketplaces at once, sharing the same code.
Where are keys for several accounts stored?
In ~/.marketplace-mcp/cabinets.json with 600 permissions outside the repo, with switching between accounts available right in the chat.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail