Yandex Wiki MCP with PKCE authorization
yandex-wiki-mcp
A Yandex Wiki MCP server with built-in browser-based PKCE authorization, no manual OAuth app setup required
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Can create and edit corporate wiki pages
- The local token grants access to the whole organization while it is valid
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/brekhov-ilya-yandex-wiki-mcpDetects 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 and edit corporate wiki pages
- The local token grants access to the whole organization while it is valid
This is third-party code. Review the repository files before installing.
What it does
The server lets AI assistants read, create and edit pages in a corporate Yandex Wiki. Authorization is handled by a built-in OAuth client using PKCE (RFC 7636): running npx yandex-wiki-mcp --auth once opens a browser to sign in and stores the token locally at ~/.config/yandex-wiki-mcp/token.json with owner-only permissions, refreshing it automatically via refresh_token when it expires. You can also use your own OAuth app with a client-id. It supports both Yandex 360 for business via org-id and a Yandex Cloud Organization via cloud-org-id.
Who it is for. For teams who want simple Yandex Wiki authorization without setting up their own OAuth app
Good fit when
- You want to connect an agent to Yandex Wiki quickly without visiting the OAuth console
- You want automatic token refresh without manually signing in again
- You need support for both Yandex 360 and a Yandex Cloud Organization
Not a fit when
- You need tight control over your own OAuth app from the start
- There is no browser access on the machine doing the initial authorization
Example request
Open the policy page in Yandex Wiki and update the vacation sectionMCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
YANDEX_ORG_ID- Yandex 360 for business organization id
YANDEX_CLOUD_ORG_ID- Yandex Cloud organization id, used instead of YANDEX_ORG_ID
Limitations
The project has no stars, a single author, and the README does not confirm an npm release. Initial authorization needs a local browser on port 27312 for the redirect URI, which complicates running it on a headless server without port forwarding.
How to disable. Remove the server from your MCP client config and delete the token file at ~/.config/yandex-wiki-mcp/token.json.
FAQ
Do I need to create an OAuth app manually?
No, a built-in PKCE client is used by default. Your own app is only needed if you want to supply a custom client-id.
Where is the token stored?
At ~/.config/yandex-wiki-mcp/token.json with 0600 permissions; the server refreshes it automatically on expiry.
Discussion
No questions or reviews yet.
Related
All Yandex Wiki toolsYandex 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
An MCP server for Yandex Wiki authenticated with a Yandex Cloud IAM token: 12 tools for pages, subpages, comments and attachments
An MCP server for Yandex Wiki: read pages by slug or URL, create, update and append, with a read-only mode
Yandex Wiki MCP server
MCP-сервер Яндекс Вики
Yandex Wiki official MCP: an agent searches and reads knowledge base pages, builds summaries and creates new pages on behalf of the employee
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
A Python read-only Yandex Wiki MCP server where each user signs in through a browser form with an IAM token
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 with PKCE authorization (this card) | no | OAuth | 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 | no | API key | 0 | Node.js |
README in short
The README describes a single connection flow for any MCP client: get a token once locally, add the server to the config, restart the client. It gives examples for Claude Code, Claude Desktop, Cursor and Codex CLI, explains the difference between Yandex 360 and a Yandex Cloud Organization, and the PKCE authorization mechanism with no client_secret.