yawiki: read-only Yandex Wiki MCP
yawiki
A Python read-only Yandex Wiki MCP server where each user signs in through a browser form with an IAM token
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Only reads pages, attachments and tables, no write operations
- The server handles users' IAM tokens during form sign-in
Install
Manual install
cp deploy/dev.env .env && uv sync && uv run yawikiLocal run, the server starts at http://localhost:8000.
This is third-party code. Review the repository files before installing.
What it does
The server provides four read-only tools: page content by URL or slug, a list of child pages for navigating the wiki structure, a list of files attached to a page, and a list of dynamic tables on a page. Its distinct feature is authorization: it runs as a remote HTTP MCP, and each user, not the server owner, signs in through a browser form entering their own Yandex Cloud IAM token and organization id, after which tools act on their behalf. It has a health check and a configurable wiki root path via an environment variable.
Who it is for. For teams that want a shared wiki-reading server for multiple users without sharing one common token
Good fit when
- Several people need to read the wiki through one deployed server under their own access rights
- You only need to view pages, attachments and tables without editing
- You need a Docker deployment with a health check
Not a fit when
- You need to create or edit pages: the server is read-only
- You need a local stdio run without standing up an HTTP server
Example request
Show the content of the homepage/platforma-neuro page in Yandex Wiki and list its child pagesLimitations
The project has no stars, a single author. It is read-only, with no write operations. Each user has to get their own IAM token via yc iam create-token or the Yandex Cloud console, and it has a limited lifetime.
How to disable. Stop it with docker compose down or stop the server process, and remove it from your MCP client config.
MCP
- Transport
- http
- Authentication
- OAuth
| Environment variables | |
|---|---|
| HOST | Listen address, defaults to 0.0.0.0 |
| PORT | Server port, defaults to 8000 |
| MCP_SERVER_PUBLIC_URL | The server's public URL for production |
| OAUTH_TOKEN_TYPE | Token type, defaults to Bearer |
| YANDEX_WIKI_BASE_SLUG | Wiki root path, e.g. homepage/platforma-neuro |
Security check
- Only reads pages, attachments and tables, no write operations
- The server handles users' IAM tokens during form sign-in
README in short
The README describes the server as a read-only Yandex Wiki MCP with browser-form IAM token authorization per user. It lists four tools, a local run via uv, a Docker run on port 8001 with a health check, and an environment variable table for host, port, public URL and wiki root path.
FAQ
Can the server edit pages?
No, it only reads content, child pages, attachments and tables.
Is there one shared token for all users?
No, each user signs in through their own form with their own IAM token; the server does not hold one shared key.
Related
Microsoft's utility and MCP server that turn PDF, Word, Excel, PowerPoint, HTML and other files into Markdown for models
Anthropic skills
Skills
Anthropic's official skill examples: docx, pdf, pptx and xlsx documents, design, MCP builder and the Agent Skills spec
A skill that builds editable PPTX decks from PDF, DOCX, URLs and Markdown with native shapes, charts and animations
A skill that draws editorial diagrams as standalone HTML and SVG files: architecture, flowcharts, ER, funnels and about forty more types