yandex-wiki-mcp

A Node.js MCP server for Yandex Wiki with 9 tools, authorized either with a Yandex Cloud CLI IAM token or an OAuth token

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • Can create, edit, move and delete Wiki pages
  • The IAM token and yc iam create-token grant access to the whole Yandex Cloud organization, not just Wiki
All reasons and checks
Russian stack

qstyle/yandex-wiki-mcp

Install

Manual install

git clone https://github.com/qstyle/yandex-wiki-mcp.git && cd yandex-wiki-mcp && npm install && npm run build

Build from source, npm run dev is available for watch mode.

Access and checks

How we review

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

  • Can create, edit, move and delete Wiki pages
  • The IAM token and yc iam create-token grant access to the whole Yandex Cloud organization, not just Wiki

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

What it does

The server provides 9 tools for reading and editing Yandex Wiki pages: get a page by slug or id, list subpages, search, create, update, append, delete and move a page. It is built from source with npm install and npm run build, and run through a bash wrapper that mints a fresh IAM token with yc iam create-token before starting the server. As an alternative it also accepts a plain Yandex OAuth token with the wiki:write scope instead of IAM.

Who it is for. For developers with the Yandex Cloud CLI on hand who need a basic set of Wiki page operations.

Good fit when

  • You have the Yandex Cloud CLI (yc) and an organization in Yandex 360 or Yandex Cloud
  • Building the Node.js project from source manually is fine
  • 9 basic operations are enough, without grids or attachments

Not a fit when

  • You need dynamic tables, attachments or comments
  • You have no Yandex Cloud CLI and do not want to set up an OAuth app manually

Example request

Update the team/policies page, append a section about remote work

MCP

Transport
stdio
Authentication
API key

Environment variables

WIKI_IAM_TOKEN required, secret
IAM token from yc iam create-token, or an OAuth token with the wiki:write scope
WIKI_ORG_ID required
Organization ID, numeric for Yandex 360, alphanumeric for Yandex Cloud
WIKI_BASE_URL
API base URL, defaults to https://api.wiki.yandex.net

Limitations

The IAM token from yc iam create-token lives at most 12 hours, refreshed by the wrapper script on every server start, so the client must restart the process. No grids, attachments or comments. No npm package, manual build.

How to disable. Remove the yandex-wiki server from your MCP client settings and, if you used the launch script, the yandex-wiki-mcp.sh file itself.

FAQ

Is the Yandex Cloud CLI required?

No, a plain Yandex OAuth token with the wiki:write scope works in the same WIKI_IAM_TOKEN variable instead of an IAM token.

How does the server detect the organization type?

Automatically from the WIKI_ORG_ID format: a numeric id is treated as Yandex 360 and gets the X-Org-Id header, an alphanumeric one as Yandex Cloud with X-Cloud-Org-Id.

Discussion

No questions or reviews yet.

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

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 access1Repository stars
Russian stack

An MCP server with 28 tools for the Yandex Wiki API v1: pages, attachments, comments, tables and recovering deleted pages

MCP serverExtended access
Russian stack

A minimal Node.js MCP server for Yandex Wiki: 10 tools for reading and editing pages, each honestly marked by how well it was tested

MCP serverExtended access2Repository stars
Russian stack

A Yandex Wiki MCP server with built-in browser-based PKCE authorization, no manual OAuth app setup required

MCP serverExtended access

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialAuthenticationRepository starsMain difference
yandex-wiki-mcp (this card)noAPI key0
Yandex Wiki MCPnoOAuth9read and edit wiki pages
Yandex Wiki MCP with grids and 3-way mergenoOAuth0tables
Yandex Wiki MCP with PKCE authorizationnoOAuth0browser sign-in

README in short

The English README lists the 9 tools in a table, prerequisites (Node.js 18+, Yandex Cloud CLI), building from source, creating a launch script that refreshes the IAM token, and registering with Claude Code. It separately covers using a plain OAuth token instead of IAM. MIT license.

README badge

Report a problem