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
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
- 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
Install
Manual install
docker compose up --buildAfter cp .env.example .env and filling in YCLIENTS_PARTNER_TOKEN. Check with curl http://localhost/health.
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 OzonLimitations
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.
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 |
Security check
- 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
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.
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.
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