yandex-wiki-mcp
An MCP server for Yandex Wiki with 30 tools: pages, attachments, comments, grids, page moves via clone, and deletion
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- Can create, move (via clone and delete) and delete pages and attachments
- The move operation irreversibly deletes the original after cloning
Install
- Works in
- Services
Manual install
git clone https://github.com/in5pirer/yandex-wiki-mcp.git && cd yandex-wiki-mcp && pip install -r requirements.txt && cp .env.example .envFill in .env with your credentials after installing.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Can create, move (via clone and delete) and delete pages and attachments
- The move operation irreversibly deletes the original after cloning
This is third-party code. Review the repository files before installing.
What it does
The server covers most of the Yandex Wiki API: reading and editing pages, edit history, attachments through the Upload Sessions API, threaded comments, watchers and dynamic tables. It also handles an honest problem head-on: the Wiki API has no real move or rename, so wiki_move_page is implemented as clone-then-delete with a success check, and wiki_move_subtree moves a page with its descendants, rolling back already-created clones on partial failure. The changelog documents fixing a false-positive bug where an older version reported a move as successful even though the update endpoint does not accept a slug field.
Who it is for. For developers who need the most complete Yandex Wiki toolset, including page moves and attachment handling.
Good fit when
- You need 30 tools, including edit history, comments and attachments
- You need to move a page or a whole subtree even though the API has no direct move
- You work through Cursor and are fine setting up the Python server manually
Not a fit when
- You need a ready package without git clone and pip install
- You need id, comments and edit history to survive a page move: the API does not preserve them
Example request
Move the old-team/notes page to new-team/notes along with all its subpages, first show the plan without writingMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
YANDEX_WIKI_TOKENrequired, secret- OAuth token from an app with Wiki access
YANDEX_WIKI_ORG_IDrequired- Organization ID from the Yandex Cloud Console
YANDEX_WIKI_ORG_TYPE- cloud or 360
Limitations
wiki_search_pages does not do full-text search: the API does not support it, the tool only matches an exact slug. Moving a page physically changes its page_id, comments and edit history do not carry over. Cursor must be restarted after code changes. No published package, manual install via git clone and pip.
How to disable. Remove the yandex-wiki block from ~/.cursor/mcp.json or your client's config.
FAQ
Why does Wiki have no real move?
The README cites Yandex's own release notes: page moving is a web-interface-only feature, the API only offers clone followed by deleting the original.
Does wiki_search_pages do text search?
No, the Yandex Wiki API has no full-text search, the tool only matches an exact slug. Use wiki_get_descendants_by_slug to browse a section.
Discussion
No questions or reviews yet.
Related
All Yandex Wiki toolsMCP server for Yandex Wiki built on the ya-wiki-api package: 36 tools for pages, grids, attachments and a section-tree cache
Yandex Wiki MCP by 1gory
mcp-yandex-wiki
An MCP server with 28 tools for the Yandex Wiki API v1: pages, attachments, comments, tables and recovering deleted pages
Yandex Wiki MCP with grid table support
Yet Another Yandex Wiki MCP Server
An MCP server for the Yandex Wiki API with pages, attachments, token-based recovery, and a rare full toolset for dynamic tables (grids)
An MCP server for Yandex Wiki: read pages by slug or URL, create, update and append, with a read-only mode
Yandex Wiki MCP with grids and 3-way merge
Yandex Wiki MCP Server
A Yandex Wiki MCP server for pages and dynamic tables, with 3-way merge support when updating content
An MCP server for Yandex Wiki authenticated with a Yandex Cloud IAM token: 12 tools for pages, subpages, comments and attachments
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| yandex-wiki-mcp (this card) | no | API key | 0 | |
| Yandex Wiki MCP | no | OAuth | 9 | read and edit wiki pages |
| Yandex Wiki MCP with grids and 3-way merge | no | OAuth | 0 | tables |
| Yandex Wiki MCP with PKCE authorization | no | OAuth | 0 | browser sign-in |
README in short
The Russian README lists 30 tools by section: reading, editing, files, comments, watchers, grids. It shows installation via git clone and pip, .env setup and Cursor wiring. Separate v0.4.0 and v0.3.0 changelog sections honestly describe bugs found and fixed, including a false-positive page-move success, plus a table of known API limitations.