SkillFoxx

Self-hosted DataLens OSS MCP server

DataLens OSS API и MCP

A translator from the cloud DataLens API to internal open-source DataLens 2.9.0 calls, plus a Streamable HTTP MCP server on top

  • 5 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • The tokens grant read and write access to your self-hosted DataLens's workbooks and dashboards
  • The containers join the existing docker network of your DataLens install
All reasons and checks
Russian stack

denisismagilov/datalens-oss-api-and-mcpAuthor:DenisIsmagilov

Install

Services

Manual install

docker compose up -d --build

Needs an already-running DataLens OSS and a filled-in .env; the MCP endpoint appears at http://127.0.0.1:8394/mcp.

Access and checks

How we review

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

  • The tokens grant read and write access to your self-hosted DataLens's workbooks and dashboards
  • The containers join the existing docker network of your DataLens install

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

What it does

The project solves a specific problem: the open-source version of DataLens (self-hosted, a docker compose with us, auth, control-api and meta-manager services) has no public API matching the cloud DataLens Public API format. The datalens-api service turns cloud-format POST /rpc/<method> calls into internal HTTP requests to the OSS services, and datalens-mcp on top of it exposes MCP tools over Streamable HTTP. The repository does not spin up the DataLens database, US or UI itself and does not touch the user's existing docker-compose.yaml; its containers just join the already-running docker network.

Who it is for. For teams running a self-hosted open-source DataLens who want to give an agent access to it in the same format as the cloud version.

Good fit when

  • You already run DataLens OSS 2.9.0 via the official docker compose and need MCP on top of it
  • You need access to workbooks, charts and dashboards of a self-hosted DataLens in the cloud API format
  • You need a separate layer that does not touch your existing DataLens configuration

Not a fit when

  • You use the cloud Yandex DataLens, not a self-hosted version: for that you need a server that talks to the cloud Public API directly
  • You do not run DataLens OSS version 2.9.0: the README says plainly that other versions were not tested

Example request

List the workbooks in our self-hosted DataLens and open the most recently created dashboard

MCP

Transport
http
Authentication
API key

Environment variables

US_MASTER_TOKEN required, secret
United Storage master token from your DataLens OSS .env.
AUTH_LOGIN required
Login for the DataLens OSS auth service, often admin by default.
AUTH_PASSWORD required, secret
Password for the auth service; the README advises changing it from the default.
MCP_AUTH_TOKEN required, secret
Token the MCP server checks in the Authorization header.

Limitations

Tested only against DataLens OSS v2.9.0; the author does not promise other versions work. It needs an already-running DataLens via the official docker compose and deploys nothing itself. The default AUTH_* login and password in the OSS version are often admin/admin, and the README advises changing them. This is an unofficial project, unrelated to Yandex or datalens-tech/datalens.

How to disable. Stop the project's containers (docker compose down) and remove the server from your MCP client config.

FAQ

Does the project spin up DataLens itself?

No, it needs an already-running DataLens OSS via the official docker compose; this repository only adds an API translator and MCP on top of it.

Does it work for cloud Yandex DataLens?

No, the project solves a problem specific to the open-source version; cloud DataLens already has its own Public API.

How is this project different from cloud Yandex DataLens?

The project fills a gap: open self-hosted DataLens 2.9.0 has no public API in the cloud DataLens Public API format. It translates the cloud API into internal calls of the open-source version and runs an MCP server on top over Streamable HTTP.

Does the project run DataLens itself and does it fit cloud DataLens?

No, DataLens itself must be deployed separately through docker compose. The project targets the self-hosted version, and cloud DataLens has its own public API. Run docker compose up -d --build. It connects to Cursor.

Discussion

No questions or reviews yet.

All DataLens tools
Official

The official DataLens MCP server from the development team: turns the public DataLens API into three gateway tools instead of hundreds of separate MCP tools

MCP serverExtended access4
Russian stack

A Rust MCP server for the Yandex DataLens public API: 60 methods via a full catalog, typed wrappers for common operations and IAM auth

MCP serverExtended access5
Russian stack

MCP server for the Yandex DataLens public API: 70 tools for dashboards, charts, datasets and connections

MCP serverExtended access8

DataLens Dev MCP

datalens-dev-mcp

Russian stack

Local MCP server and Codex plugin for Yandex DataLens dashboard development: read, author, publish, back up and clean up objects

MCP serverBroad access7
Official

Official DataLens (Yandex) skills for Claude Code, Codex and OpenCode: SDK, HTML reports and RLS resolution

SkillExtended access13

A Java MCP server for querying Postgres, MySQL and SQLite in plain language, unrelated to the Yandex DataLens service

MCP serverBroad access

README in short

The Russian README explains the project as a translator from the cloud API to open-source DataLens 2.9.0 calls, states its unofficial status and MIT license plainly, gives a table of the two services with default ports, a quick start with .env setup and a curl check, and links to separate docs on install, configuration, the RPC API, MCP, security and errors.

README badge

Report a problem