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

brekhov-ilya/yandex-wiki-mcpAuthor:Ilya Brekhov

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/brekhov-ilya-yandex-wiki-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal

claude mcp add --transport stdio yandex-wiki -- npx -y yandex-wiki-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "yandex-wiki": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-wiki-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "yandex-wiki": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-wiki-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

code --add-mcp '{"name":"yandex-wiki","type":"stdio","command":"npx","args":["-y","yandex-wiki-mcp"]}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "yandex-wiki": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "yandex-wiki-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add yandex-wiki -- npx -y yandex-wiki-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.yandex-wiki]
command = "npx"
args = ["-y", "yandex-wiki-mcp"]

If the file already exists, append the block to the end.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "yandex-wiki": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-wiki-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "yandex-wiki": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-wiki-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "yandex-wiki": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-wiki-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "yandex-wiki": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-wiki-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "yandex-wiki": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "yandex-wiki-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "yandex-wiki": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-wiki-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "yandex-wiki": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-wiki-mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

YANDEX_ORG_IDoptional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit be60cc1.

Text for your agent

Find your organization's org-id (Yandex 360) or cloud-org-id (Yandex Cloud), run npx -y yandex-wiki-mcp --org-id YOUR_ID --auth once to sign in via browser, then add the server to your client config with the YANDEX_ORG_ID or YANDEX_CLOUD_ORG_ID variable.

Other ways from the author

npx -y yandex-wiki-mcp --org-id YOUR_ORG_ID --auth

One-time browser authorization; for Yandex Cloud use --cloud-org-id instead of --org-id.

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 section

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.

MCP

Transport: stdio
Authentication: OAuth

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

Security check

Can create and edit corporate wiki pages
The local token grants access to the whole organization while it is valid

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.

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.

MarkItDown

Official

Microsoft's utility and MCP server that turn PDF, Word, Excel, PowerPoint, HTML and other files into Markdown for models

MCP serverMedium riskNo VPN needed187.4K

Anthropic skills

Skills

Editors’ pick

Anthropic's official skill examples: docx, pdf, pptx and xlsx documents, design, MCP builder and the Agent Skills spec

SkillMedium risk178.8K

PPT Master

Editors’ pick

A skill that builds editable PPTX decks from PDF, DOCX, URLs and Markdown with native shapes, charts and animations

SkillMedium risk56.8K

Diagram Design

Editors’ pick

A skill that draws editorial diagrams as standalone HTML and SVG files: architecture, flowcharts, ER, funnels and about forty more types

SkillMedium riskNo VPN needed42.6K

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

MarkItDown

Anthropic skills

PPT Master

Diagram Design