yawiki MCP
A Python MCP server and CLI for Yandex Wiki: create, read, update and delete pages by slug
- 1 ★ on the repository
- Last commit
Extended access
Why this level
- Can create, edit and delete Wiki pages through CRUD operations
- The OAuth token is passed via environment variables in the client config
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/yawikiDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Can create, edit and delete Wiki pages through CRUD operations
- The OAuth token is passed via environment variables in the client config
This is third-party code. Review the repository files before installing.
What it does
The server gives an agent six tools for Yandex Wiki: create a page, read, update, delete, check existence, and get-or-create. Besides the MCP server the package ships a standalone yawiki-cli command for the same operations straight from a terminal, without an agent. A default base slug set via YANDEX_WIKI_BASE_SLUG scopes operations to a users/your-login namespace.
Who it is for. For developers who need a simple CRUD toolset over a personal or team Yandex Wiki space.
Good fit when
- You need a small operation set: create, read, update, delete a page
- You want both an MCP version for an agent and a standalone CLI for scripts
- Installing via uvx straight from the git repository is fine
Not a fit when
- You need dynamic tables, attachments or full-text search
- You need to work across an arbitrary page tree rather than one base slug
Example request
Create a Wiki page at scenarios/onboarding titled Onboarding planMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
YANDEX_WIKI_TOKENrequired, secret- Yandex OAuth token, obtained at oauth.yandex.ru
YANDEX_TRACKER_ORG_IDrequired- Organization ID, found in Yandex Tracker settings
YANDEX_WIKI_BASE_SLUG- Base slug for the page space, e.g. users/your_username
Limitations
Only six tools, no grids, attachments or search. The org id variable is confusingly named YANDEX_TRACKER_ORG_ID even though it refers to the Wiki organization. No PyPI package, install via uvx --from git+... or git clone.
How to disable. Remove the yandex-wiki block from your MCP client config.
FAQ
Why is the org id variable named YANDEX_TRACKER_ORG_ID for Wiki?
The README explains the org ID can be found in Yandex Tracker settings, because Tracker and Wiki share the same Yandex 360 organization.
Can it be used without an MCP client?
Yes, the package ships yawiki-cli with the same create, read, update, delete, exists operations straight from a terminal.
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
An MCP server for Yandex Wiki with 30 tools: pages, attachments, comments, grids, page moves via clone, and deletion
An MCP server for Yandex Wiki: read pages by slug or URL, create, update and append, with a read-only mode
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
A Python read-only Yandex Wiki MCP server where each user signs in through a browser form with an IAM token
An MCP server for Yandex Wiki authenticated with a Yandex Cloud IAM token: 12 tools for pages, subpages, comments and attachments
README in short
The Russian README shows installation via uvx and via git clone with uv sync, three environment variables, a table of the six MCP tools and Python call examples. It separately covers yawiki-cli with the same operations for direct terminal use. MIT license.