SkillFoxx

Wildberries and Ozon remote MCP server

Marketplace Claude Remote MCP Server

A self-hosted remote MCP server: an admin configures Wildberries and Ozon accounts, users connect through OAuth without their own keys

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • The server stores the admin's real Wildberries and Ozon keys on its own infrastructure
  • Per its description the tools only read ad, analytics and financial data
All reasons and checks
Russian stack

an1ksx/ozon_n_wb_mcp_serverAuthor:An1kSX

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/marketplace-claude-remote-mcp-server

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

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The server stores the admin's real Wildberries and Ozon keys on its own infrastructure
  • Per its description the tools only read ad, analytics and financial data

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

What it does

A Node.js server exposes a public remote MCP endpoint with OAuth 2.1: an administrator enters Wildberries and Ozon keys in a separate protected admin panel, and users connect through Claude via a connector link, signing in with a service account without ever seeing the marketplace keys themselves. The server exposes read-only tools for ad stats, analytics and finance across both marketplaces. Deployment targets Docker Compose with Postgres and Redis, with public HTTPS through a built-in Caddy proxy.

Who it is for. For agencies and teams who want to give several people access to Wildberries and Ozon data through Claude without handing out marketplace keys.

Good fit when

  • You need shared Wildberries and Ozon analytics access for a team without handing out API keys
  • You need a remote Claude connector with its own OAuth sign-in
  • You can deploy and maintain a Docker setup with a public domain

Not a fit when

  • You need a personal server for your own single account without Postgres and Redis infrastructure
  • You have no public domain or way to keep the service online
  • You need to write data; per its description the server only reads

Example request

Show Wildberries ad campaign stats and the Ozon financial summary for last month

MCP

Transport
http
Authentication
OAuth

Environment variables

PUBLIC_HOST required
The server's public domain for certificate issuance.
BASE_URL required
The service's base public URL.
ACME_EMAIL required
Email for Let's Encrypt certificate issuance through Caddy.

Limitations

It needs your own public domain, with ports 80 and 443 reachable from the internet for certificate issuance. All authenticated users see every account the admin configured; the README does not describe role-based separation. Deployment needs Docker, Postgres and Redis, not a one-command run. The server runs on someone else's infrastructure, so if you are not the admin, you are trusting marketplace keys to the service operator.

How to disable. Disable the connector in Claude's settings; the admin needs to run docker compose down on the server to stop it fully.

FAQ

Does the user see the Wildberries and Ozon keys?

No, the keys stay only on the admin's server; the user signs in through OAuth with a service account.

Can it run without Docker?

The README also describes a local npm run dev run, but production and HTTPS assume Docker Compose.

Discussion

No questions or reviews yet.

All Ozon tools
Russian stack

A Cloudflare Workers MCP server with sales, stock and review presets for Wildberries and Ozon, plus universal access to any method of both APIs

MCP serverBroad access
Russian stack

A remote MCP server on top of the MPSTATS API: Wildberries, Ozon and Yandex Market analytics as a Claude connector

MCP serverExtended access
Russian stack

Remote Sellmonitor MCP servers for Wildberries analytics: market and competitors, plus your own store's sales, costs and profit

MCP serverExtended access13

YClients and Ozon MCP servers, one deployment

MCP Servers — Combined Deployment

Russian stack

A docker-compose deployment of two MCP servers behind one nginx: full YClients booking API access and an Ozon storefront reader via a headless browser

MCP serverBroad access

README in short

The README describes the security model: Claude connects over public HTTPS, only the server holds marketplace keys, and OAuth tokens are required for every tool. It covers a local npm run, Docker Compose deployment with Postgres and Redis, public domain setup with automatic Caddy certificates, a health check, and setting up the Claude connector alongside an admin panel for adding accounts.

README badge

Report a problem