bi-mcp: Metrika, GSC, Wildberries and Ozon analytics combine
bi-mcp
An MCP server on Cloudflare Workers combines Yandex Metrika, Google Search Console, Wildberries and Ozon into one summary for a shop owner
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Stores Metrika, GSC, Wildberries and Ozon keys as Cloudflare Workers secrets
- Per the code the tools only read statistics and do not change prices, stock or orders
Install
Manual install
npx wrangler secret put MCP_SECRET
npx wrangler secret put METRIKA_TOKEN
npx wrangler secret put OZON_CLIENT_ID
npx wrangler secret put OZON_API_KEY
npx wrangler deployThe set of secrets depends on which sources you connect; the full list is in the README.
This is third-party code. Review the repository files before installing.
What it does
The server is deployed as a single Cloudflare Worker and gives an agent tools for four sources: bi_overview builds one summary across all connected services for a period, metrika_traffic and metrika_request cover Yandex Metrika down to an arbitrary API path, and separate tools cover Google Search Console, Wildberries sales and stock, and Ozon Seller API data. Every source is optional: if a secret or key is missing for it, the summary block just explains why, while the other sources still run.
Who it is for. For Wildberries and Ozon shop owners who want one combined view of site and sales data without switching between services.
Good fit when
- You need one combined view of site traffic and marketplace sales for a period
- You need general access to Yandex Metrika API methods without a separate client
- You have a Cloudflare account for a free worker deploy
Not a fit when
- You need tools to change prices, stock or orders; the server does not provide them
- You have none of the four data sources and do not need them
- You have no experience with Cloudflare Workers secrets
Example request
Give me a summary of site traffic, search rankings and Wildberries and Ozon sales for the last 30 daysLimitations
The server must be deployed by you on Cloudflare Workers; there is no ready public address. Each source needs its own set of secrets: Metrika OAuth, Google Search Console OAuth, a Wildberries statistics token, and an Ozon Client-Id and Api-Key. The MCP_SECRET is embedded right in the connection URL rather than passed as a separate header, worth keeping in mind when storing the link. The code fits in one file, and the README does not describe the underlying APIs' rate limits.
How to disable. Remove the connector from your MCP client settings and delete the worker in the Cloudflare dashboard if it is no longer needed.
MCP
- Transport
- http
- Authentication
- API key
| Environment variables | |
|---|---|
| MCP_SECRET required, secret | The secret for your worker's connection URL. |
| METRIKA_TOKEN secret | Yandex Metrika OAuth token. |
| GSC_CLIENT_ID secret | Google Search Console OAuth Client Id. |
| GSC_CLIENT_SECRET secret | Google Search Console OAuth Client Secret. |
| GSC_REFRESH_TOKEN secret | Google Search Console OAuth refresh token. |
| WB_TOKEN secret | Wildberries supplier statistics token. |
| OZON_CLIENT_ID secret | Ozon Seller API Client Id. |
| OZON_API_KEY secret | Ozon Seller API key. |
Security check
- Stores Metrika, GSC, Wildberries and Ozon keys as Cloudflare Workers secrets
- Per the code the tools only read statistics and do not change prices, stock or orders
README in short
The Russian README describes the server as combined analytics over Metrika, Google Search Console, Wildberries and Ozon on Cloudflare Workers, gives the connector URL with the secret in the path, and lists the secrets each source needs. It lists the tools: a combined summary, Metrika traffic and a generic request tool, and matching tools for the other sources.
FAQ
Do I need to connect all four sources?
No, each source is optional; a missing one just shows the reason it was skipped in the combined summary.
Can the server change prices or stock?
No, based on the code these are read-only statistics and analytics tools.
Related
Official DataLens (Yandex) skills for Claude Code, Codex and OpenCode: SDK, HTML reports and RLS resolution
A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata
An open MCP server and agent skill set for SEO: keyword research, competitors, backlinks and site audits powered by DataForSEO
A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents