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

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/yandex-360-mcp-server

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Assembled automatically, review before installing.

Run in a terminal

claude mcp add --transport stdio --env 'WIKI_TOKEN=<your WIKI_TOKEN>' --env 'WIKI_ORG_ID=<WIKI_ORG_ID value>' yandex360 -- uvx yandex360-mcp@latest

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "yandex360": {
      "command": "uvx",
      "args": [
        "yandex360-mcp@latest"
      ],
      "env": {
        "WIKI_TOKEN": "<your WIKI_TOKEN>",
        "WIKI_ORG_ID": "<WIKI_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "yandex360": {
      "command": "uvx",
      "args": [
        "yandex360-mcp@latest"
      ],
      "env": {
        "WIKI_TOKEN": "<your WIKI_TOKEN>",
        "WIKI_ORG_ID": "<WIKI_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

code --add-mcp '{"name":"yandex360","type":"stdio","command":"uvx","args":["yandex360-mcp@latest"],"env":{"WIKI_TOKEN":"<your WIKI_TOKEN>","WIKI_ORG_ID":"<WIKI_ORG_ID value>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "yandex360": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "yandex360-mcp@latest"
      ],
      "env": {
        "WIKI_TOKEN": "<your WIKI_TOKEN>",
        "WIKI_ORG_ID": "<WIKI_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add yandex360 --env 'WIKI_TOKEN=<your WIKI_TOKEN>' --env 'WIKI_ORG_ID=<WIKI_ORG_ID value>' -- uvx yandex360-mcp@latest

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.yandex360]
command = "uvx"
args = ["yandex360-mcp@latest"]
env = { WIKI_TOKEN = "<your WIKI_TOKEN>", WIKI_ORG_ID = "<WIKI_ORG_ID value>" }

If the file already exists, append the block to the end.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

gemini mcp add -s user -e 'WIKI_TOKEN=<your WIKI_TOKEN>' -e 'WIKI_ORG_ID=<WIKI_ORG_ID value>' yandex360 uvx yandex360-mcp@latest

Or add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "yandex360": {
      "command": "uvx",
      "args": [
        "yandex360-mcp@latest"
      ],
      "env": {
        "WIKI_TOKEN": "<your WIKI_TOKEN>",
        "WIKI_ORG_ID": "<WIKI_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "yandex360": {
      "command": "uvx",
      "args": [
        "yandex360-mcp@latest"
      ],
      "env": {
        "WIKI_TOKEN": "<your WIKI_TOKEN>",
        "WIKI_ORG_ID": "<WIKI_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "yandex360": {
      "command": "uvx",
      "args": [
        "yandex360-mcp@latest"
      ],
      "env": {
        "WIKI_TOKEN": "<your WIKI_TOKEN>",
        "WIKI_ORG_ID": "<WIKI_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "yandex360": {
      "command": "uvx",
      "args": [
        "yandex360-mcp@latest"
      ],
      "env": {
        "WIKI_TOKEN": "<your WIKI_TOKEN>",
        "WIKI_ORG_ID": "<WIKI_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "yandex360": {
      "type": "local",
      "command": [
        "uvx",
        "yandex360-mcp@latest"
      ],
      "environment": {
        "WIKI_TOKEN": "<your WIKI_TOKEN>",
        "WIKI_ORG_ID": "<WIKI_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "yandex360": {
      "command": "uvx",
      "args": [
        "yandex360-mcp@latest"
      ],
      "env": {
        "WIKI_TOKEN": "<your WIKI_TOKEN>",
        "WIKI_ORG_ID": "<WIKI_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "yandex360": {
      "command": "uvx",
      "args": [
        "yandex360-mcp@latest"
      ],
      "env": {
        "WIKI_TOKEN": "<your WIKI_TOKEN>",
        "WIKI_ORG_ID": "<WIKI_ORG_ID value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

WIKI_TOKENsecret, required: Yandex OAuth token with wiki:read / wiki:write scopes
WIKI_ORG_IDrequired: Yandex 360 organization ID

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: uv

Checked against the repository on Sep 26, 2026, commit 5d65c3d.

Text for your agent

Add a server to your client config with the command uvx yandex360-mcp@latest and the variables WIKI_TOKEN (OAuth token with wiki:read or wiki:write scope) and WIKI_ORG_ID.

Other ways from the author

{
  "mcpServers": {
    "yandex360": {
      "type": "stdio",
      "command": "uvx",
      "args": ["yandex360-mcp@latest"],
      "env": {
        "WIKI_TOKEN": "${WIKI_TOKEN}",
        "WIKI_ORG_ID": "${WIKI_ORG_ID}"
      }
    }
  }
}

Snippet for .mcp.json from the README, also available via claude mcp add.

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

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.

MCP

Transport: stdio
Authentication: API key

Environment variables
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

Security check

The Wiki module can create, edit and delete pages
A write-scoped OAuth token is passed through environment variables

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.

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.

MarkItDown

Official

Microsoft's utility and MCP server that turn PDF, Word, Excel, PowerPoint, HTML and other files into Markdown for models

MCP serverMedium riskNo VPN needed187.4K

Anthropic skills

Skills

Editors’ pick

Anthropic's official skill examples: docx, pdf, pptx and xlsx documents, design, MCP builder and the Agent Skills spec

SkillMedium risk178.8K

PPT Master

Editors’ pick

A skill that builds editable PPTX decks from PDF, DOCX, URLs and Markdown with native shapes, charts and animations

SkillMedium risk56.8K

Diagram Design

Editors’ pick

A skill that draws editorial diagrams as standalone HTML and SVG files: architecture, flowcharts, ER, funnels and about forty more types

SkillMedium riskNo VPN needed42.6K

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

MarkItDown

Anthropic skills

PPT Master

Diagram Design