SkillFoxx

Yandex 360 MCP Server

A modular MCP server for Yandex 360: Wiki only for now, a service's tools appear only when its tokens are set

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

Extended access

Why this level

  • The Wiki module can create, edit and delete pages
  • A write-scoped OAuth token is passed through environment variables
All reasons and checks
Russian stack

pa1ch/yandex360-mcpAuthor:pa1ch

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/yandex-360-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 Wiki module can create, edit and delete pages
  • A write-scoped OAuth token is passed through environment variables

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

What it does

The server is organized as independent modules per Yandex 360 service, and only Wiki is implemented so far: nine tools for reading, searching, creating, updating, appending and deleting pages. Directory and Disk are on the roadmap but not built yet. A module registers its tools only when both of its environment variables are set, so an agent never sees tools for services it has not configured. The author draws a clear scope line: Yandex Tracker is deliberately out of scope, and the README points to the separate aikts/yandex-tracker-mcp server for it.

Who it is for. For people using Yandex 360 services beyond Tracker who want a server that does not waste model context on unused tools.

Good fit when

  • You only need Wiki from Yandex 360 services, without Tracker in the same server
  • It matters that unconfigured services do not expose tools to the agent
  • Installing via uvx without cloning the repo is fine

Not a fit when

  • You need Directory or Disk: not implemented yet, only on the roadmap
  • You need Tracker in the same server, the authors deliberately left it out

Example request

Find the vacation policy page in the corporate Wiki and show its content

MCP

Transport
stdio
Authentication
API key

Environment variables

WIKI_TOKEN required, secret
Yandex OAuth token with wiki:read or wiki:write scope
WIKI_ORG_ID required
Yandex 360 organization ID, sent as X-Org-Id
YANDEX360_ENABLE
Comma-separated module list to manually pin the exposed tool set

Limitations

Only the Wiki module is implemented, Directory and Disk are marked planned. Tracker is out of scope by design. Community project, not from the Yandex vendor.

How to disable. Remove the yandex360 block from your MCP client config.

FAQ

Why are there no Tracker tools?

The README states Tracker is deliberately excluded because a mature server, aikts/yandex-tracker-mcp, already exists for it, and recommends running both servers side by side.

How do I pin the module set manually?

The YANDEX360_ENABLE variable with a comma-separated list, e.g. wiki, pins the active modules even if tokens are set for more services.

Discussion

No questions or reviews yet.

All Yandex 360 tools
Russian stack

An MCP server for Yandex Wiki with 30 tools: pages, attachments, comments, grids, page moves via clone, and deletion

MCP serverExtended access
Russian stack

Two Java servers for Yandex Tracker (84 tools) and Yandex Wiki (39), with an installer, OAuth device flow and a read-only mode

MCP serverExtended access
Russian stack

An MCP server for Yandex Wiki: read pages by slug or URL, create, update and append, with a read-only mode

MCP serverBroad access9
Russian stack

An MCP server for Yandex Wiki authenticated with a Yandex Cloud IAM token: 12 tools for pages, subpages, comments and attachments

MCP serverExtended access

Yandex Wiki MCP server

MCP-сервер Яндекс Вики

Official

Yandex Wiki official MCP: an agent searches and reads knowledge base pages, builds summaries and creates new pages on behalf of the employee

MCP serverExtended access
Russian stack

MCP server for Yandex Wiki built on the ya-wiki-api package: 36 tools for pages, grids, attachments and a section-tree cache

MCP serverExtended access1

README in short

The English README (with a Russian version in README_ru.md) describes the modular architecture, a module status table (Wiki ready, Directory and Disk planned), setup for Claude Code, Claude Desktop (including a one-click .mcpb install), Cursor and VS Code, an environment variable table, and the principle of loading tools only for configured modules.

README badge

Report a problem