Spree Commerce: open-source B2B and marketplace ecommerce
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
제작자가 쓴 설명(영어 원문)
MCP server for Avito: chats, listings, orders and analytics, with previews and confirmations.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
Client_id, Client_secret, Profile_id, AVITO_MCP_PROTOCOL_ERA비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"avito": {
"command": "npx",
"args": [
"-y",
"avito-mcp"
],
"env": {
"Client_id": "your-value",
"Client_secret": "your-value",
"Profile_id": "your-value",
"AVITO_MCP_PROTOCOL_ERA": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add avito --env Client_id=your-value --env Client_secret=your-value --env Profile_id=your-value --env AVITO_MCP_PROTOCOL_ERA=your-value -- npx -y avito-mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"avito": {
"command": "npx",
"args": [
"-y",
"avito-mcp"
],
"env": {
"Client_id": "your-value",
"Client_secret": "your-value",
"Profile_id": "your-value",
"AVITO_MCP_PROTOCOL_ERA": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"avito": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"avito-mcp"
],
"env": {
"Client_id": "your-value",
"Client_secret": "your-value",
"Profile_id": "your-value",
"AVITO_MCP_PROTOCOL_ERA": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
AVITO_MCP_PROTOCOL_ERA env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 9일 점검
레지스트리 이름이 GitHub 계정 elchin92 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: Client_id, Client_secret, Profile_id
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(2.1.1)은 2개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
MCP server integrating with Stripe - tools for customers, products, payments, and more.
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Connect your AI client to your Avito account: read chats and statistics, prepare replies, and manage listings and orders.
Ask your AI client in plain language; it uses this MCP server to call the official Avito APIs. 148 tools across 18 APIs cover buyer chats, listings, statistics, promotion and orders. Run it on your computer or your own server.
You bring an AI client and an Avito account with API access. The client provides the model; this project provides the connection and tools. Automatic replies and scheduled reports need an agent or scheduler configured separately.
[Русская версия →](README.ru.md) · Documentation · Client setup · Workflows · Troubleshooting
New in v2.1.1: step-by-step setup, complete English and Russian workflow and troubleshooting guides, and explicit demo versus live-account instructions. Release notes.
| Your next step | Guide |
|---|---|
| See it work without an Avito account | Run the demo |
| Connect your own account | Quick start |
| Set up a client you already use | Client configurations |
| Deploy or contribute | Operations · Contributing |
npx -y avito-mcp@2 --demo
The demo uses fictional data: 53 listings and 2 unread chats. It runs locally, needs no Avito keys and sends no requests to Avito. It walks through a report, a price preview, confirmation and a repeated request that changes the price only once. The first npx run downloads the npm package; from source, use npm run demo.
To use your own Avito account, follow the quick start and omit `--demo`. Normal server calls use your configured account; demo data never replaces it.
| Task | Start here | Result |
|---|---|---|
| Check how your listings are doing | Morning report, analytics profile | Balance, listing activity and spending, with dates and source IDs |
| Work through buyer messages | Unread-chat triage, messenger profile | Prioritised chats and draft replies; sending is a separate confirmed action |
| Change a listing price | Preview and confirm, seller profile | Request preview, pending action, then a result to check |
Profiles use existing environment variables to expose a focused tool set. The recipes explain what to ask, which tools are involved, and how to check the result.
You need Node.js 22.12+, an MCP-capable AI client, and Avito API credentials for your account. Obtain Client_id, Client_secret, and numeric Profile_id through Avito's API account page. Available methods depend on your account's API access; installing this server does not grant additional Avito permissions.
For Claude Desktop, merge this into its MCP config using Settings → Developer → Edit Config. For Cursor, use your personal ~/.cursor/mcp.json. Replace the three placeholders locally and keep the filled config out of Git.
{
"mcpServers": { "avito": { "command": "npx", "args": ["-y", "avito-mcp@2"], "env": { "Client_id": "YOUR_CLIENT_ID", "Client_secret": "YOUR_CLIENT_SECRET", "Profile_id": "YOUR_PROFILE_ID", "AVITO_MCP_MODE": "read_only" } } } }
Restart the client and ask: “Use Avito to show my account balance and the first page of active listings. Do not change anything.” A successful answer should show your real balance and listing IDs, or an empty list if the account has no listings. The example starts in read_only; without this setting the server's default remains full_access.
VS Code, Zed, Codex and ChatGPT use their own setup formats. Copy the client-specific config, then try a workflow. The examples pin major version 2; pin an exact published version for controlled deployments.
| Client | Ready-to-copy config |
|---|---|
| Claude Desktop | JSON + setup |
| Cursor | JSON + setup |
| VS Code / Copilot | servers JSON |
| Zed | context_servers JSON |
| Codex CLI / IDE extension | TOML |
| ChatGPT desktop | Settings → MCP servers or shared TOML |
| ChatGPT web | Remote plugin setup and limits |
These are documented configurations, not a claim that every client/version has been tested against a live Avito account. Report compatibility results with the client version and operating system.
| Domain | Examples |
|---|---|
| Messenger | Chats, messages, images, subscriptions and webhook events |
| Listings and statistics | Listing details, prices, views, contacts and spending |
| Orders and stock | Delivery statuses, tracking, labels, marking codes and stock |
| Promotion | VAS, CPA bids, forecasts and promotion orders |
| Autoload | Feed uploads, reports and ID mapping |
| Account and other APIs | Balance, reviews, staff, tariffs and calls |
| Logistics partners | 3PL delivery endpoints; most sellers do not need these |
The bundled API snapshot covers 138 Swagger operations plus local and meta tools. The full manifest has 148 tools; default registration exposes 144, because token-returning tools and local image uploads require separate opt-ins. read_only exposes 80 before allowlist filtering. Inspect avito://manifest or build dist/manifest.json for exact names, schemas and risks.
Resources include the tool manifest, active configuration, rate limits, pending confirmations and webhook events. Five built-in prompts cover a daily overview, unread chats, promotion preparation, tool explanations and a safety report. Resource and prompt reference.
read_only, guarded, and full_access, plus AVITO_MCP_ALLOW_TOOLS / AVITO_MCP_DENY_TOOLS, control which tools are available.dryRun: true previews a destructive request without sending it. It does not reserve an action or validate the live account's permission to execute it.idempotencyKey deduplicates the same tool and arguments within the configured retention period. Reuse the same key for the same intended operation. If the outcome is uncertain, reconcile with Avito before retrying or choosing a new key.Business calls use the real Avito account. Start with reads and previews. Ready-to-use safety configurations describe stronger approval controls, upload boundaries and recovery.
For a hosted agent or several clients, use Streamable HTTP on your own HTTPS domain. Set AVITO_MCP_TRANSPORT=http, AVITO_MCP_HTTP_PUBLIC_URL=https://mcp.example.com, and a strong AVITO_MCP_OAUTH_OWNER_PASSWORD, together with the Avito credentials.
Deployment, OAuth, Caddy and nginx configuration. bearer and none modes do not claim conformance with the MCP authorization specification; use OAuth for clients that discover authorization automatically.
The optional receiver buffers incoming Avito events and exposes them through a tool and a subscribable resource. An external agent must consume those events and decide whether to respond. Receiver setup.
AVITO_MCP_PROTOCOL_ERA selects legacy (default, MCP 2025-11-25), dual (both revisions), or modern (MCP 2026-07-28). A default stdio installation keeps serving the legacy revision; enabling the newer revision is explicit.
AVITO_MCP_HTTP_MAX_SESSIONS and AVITO_MCP_HTTP_SESSION_IDLE_SEC apply to legacy 2025-11-25 only. Modern HTTP uses AVITO_MCP_HTTP_MAX_INFLIGHT and AVITO_MCP_HTTP_MAX_STREAMS instead. Protocol details and limits.
Public tool names, documented valid arguments, environment variables, resource URIs and prompt names follow SemVer. See versioning details, migration from 1.3.x, and CHANGELOG.
Token-returning tools and image uploads stay hidden until explicitly enabled. Tokens and runtime state are stored locally with restricted file permissions. Safety configuration, security policy and private reporting, and operational diagnostics describe the boundaries.
git clone https://github.com/elchin92/avito-mcp.git
cd avito-mcp npm ci cp .env.example .env
npm run build:release
Configure your client to run node /absolute/path/to/dist/server.js. Pass creden
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요