SkillFoxx

YClients and Ozon MCP servers, one deployment

MCP Servers — Combined Deployment

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

  • 0 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • YClients tools create and change bookings, clients, cash transactions, fiscal receipts and inventory
  • The Ozon server bypasses anti-bot protection by emulating a browser to read the storefront
  • Start with a read-only token if YClients offers one
All reasons and checks
Russian stack

ktsverkun/mcp-serversAuthor:ktsverkun

Install

Services

Manual install

docker compose up --build

After cp .env.example .env and filling in YCLIENTS_PARTNER_TOKEN. Check with curl http://localhost/health.

Access and checks

How we review

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

  • YClients tools create and change bookings, clients, cash transactions, fiscal receipts and inventory
  • The Ozon server bypasses anti-bot protection by emulating a browser to read the storefront
  • Start with a read-only token if YClients offers one

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

What it does

The repository brings up two independent MCP servers behind one nginx via docker-compose, under /yclients/mcp and /ozon/mcp. yclients-mcp-server, in Python with FastMCP, is generated from the official YClients OpenAPI spec and exposes 32 tools covering 305 operations: bookings, clients, staff, services, cash registers and finance, loyalty, inventory, receipt fiscalization, analytics. A weekly workflow checks the spec and regenerates the tool code. ozon-mcp-server, in Node.js with Playwright, does not use the official Seller API. It drives a headless browser over the Ozon.ru storefront, using natural navigation to get past anti-bot protection, and returns product search, product cards, categories and filters without any login.

Who it is for. For developers of YClients-based businesses who want an agent for bookings and finance, plus quick Ozon product lookups without integrating the Seller API.

Good fit when

  • You want an agent to create and change bookings, clients and cash transactions in YClients
  • You need quick Ozon product and price search without the official Seller API or a token
  • You want one docker-compose deployment on Timeweb Cloud App Platform or your own server

Not a fit when

  • You need only one of the two servers: it is simpler to deploy it alone than the whole monorepo
  • You need Ozon seller-account access: the server only reads the public storefront
  • You need a stable contract: the YClients spec changes over time, and Ozon can tighten its anti-bot defenses at any point

Example request

Show tomorrow's free slots in YClients and find a cheaper alternative to this product on Ozon

MCP

Transport
http
Authentication
not required

Environment variables

YCLIENTS_PARTNER_TOKEN required, secret
YCLIENTS partner token from the marketplace, required for the booking server
YCLIENTS_USER_TOKEN secret
User token for operations on a specific company's data

Limitations

A monorepo with no root license (subprojects are MIT), zero stars, a single author, no releases. The README documents deployment of only two servers, YClients and Ozon, although the repo also contains separate MCP servers for Google Calendar and captcha solving unrelated to this pairing. The Ozon server relies on bypassing the site's anti-bot protection via Playwright and can break when that protection changes. The README covers the API, not how to set up the YClients account side.

How to disable. Stop the stack with docker compose down and remove the yclients and ozon entries from your MCP client config.

FAQ

Do the Ozon tools need a token?

No, ozon-mcp-server just reads the public storefront with a browser. YCLIENTS_PARTNER_TOKEN is only needed for the YClients server.

What happens if Ozon changes its anti-bot defenses?

The README warns explicitly that Ozon's protection can change and the server may need updates; there is no stability guarantee.

Discussion

No questions or reviews yet.

All Ozon tools
Russian stack

An MCP server for the Ozon Seller API with a catalog of 441 methods, read and write access classes, and keys stored outside the repository

MCP serverBroad access3
Russian stack

An MCP server for one ozon.ru buyer account: orders, cart, favorites, selections, and, when explicitly allowed, placing and paying for an order

MCP serverBroad access9
Russian stack

An MCP server with 9 read-only tools over the Ozon Seller API v3: products, FBS and FBO orders, analytics, finance and returns

MCP serverExtended access

Ozon MCP

ozon-mcp

Russian stack

MCP server for Ozon Seller API and Performance API: method search, calls guarded against accidental writes and ready analytics workflows

MCP serverBroad access26
Russian stack

MCP server for the Ozon Seller and Performance APIs: prices, promotions, ads, orders, returns and finance across several stores

MCP serverBroad access11

Ozon Seller MCP server

mcp-ozon-seller

Russian stack

MCP server for Ozon Seller API: products, prices, stocks, FBO and FBS orders, seller analytics and finances

MCP serverBroad access7

README in short

The monorepo README describes pairing yclients-mcp-server and ozon-mcp-server behind nginx via docker-compose: directory layout, local run and curl checks, the YCLIENTS_PARTNER_TOKEN and YCLIENTS_USER_TOKEN variables, deployment steps on Timeweb Cloud App Platform choosing Docker Compose as the deploy type, and config snippets for Claude Desktop and Claude Code. The individual server READMEs list YClients tools by API section and describe the technique for bypassing Ozon's anti-bot protection via natural navigation and human-like behavior simulation.

README badge

Report a problem