Skip to main content
Glama

English | Русский

Yandex Wiki Search MCP

yandex-wiki-search-mcp MCP server PyPI Python CI codecov License Docker

Demo: search a wiki page and summarize it via MCP

Connect Claude, Cursor, Windsurf, or any MCP client to Yandex Wiki: full-text search, pages, comments, attachments, and dynamic tables ("grids") — 33 tools with typed schemas.

An unofficial project — not affiliated with or endorsed by Yandex.

  • 🔍 Full-text search across the entire wiki — the same backend that powers the Wiki web search bar, up to 50 results per query

  • 📄 Full page lifecycle — create, update, append (top / bottom / anchor), clone, delete with a recovery token, comments, file uploads

  • 📊 Dynamic tables (grids) — 11 write tools: rows, columns, cells, copy, sort

  • 🔒 Server-side read-only mode — WIKI_READ_ONLY=true simply doesn't register write tools, so the agent can't bypass it

  • 🧩 Typed tool surface — every tool ships an input JSON schema and safety annotations (read-only / destructive / idempotent hints), and all but page_read_attachment, which answers with a native image or resource block, an output schema too

  • 🐳 Runs anywhere — stdio for desktop clients, streamable-http + Docker (with optional multi-user OAuth) for teams

Quick start

  1. Get a Yandex OAuth token with Wiki access (official guide) and your organization ID.

  2. Install into your client:

Add to Cursor Install in VS Code Add to LM Studio Install in Claude Desktop

The Claude Desktop badge downloads the .mcpb bundle of the latest release — double-click it and Claude Desktop installs the server, prompting for the token and org ID (uv must be installed).

{
  "mcpServers": {
    "yandex-wiki-search": {
      "command": "uvx",
      "args": ["yandex-wiki-search-mcp"],
      "env": {
        "WIKI_TOKEN": "YOUR_TOKEN",
        "WIKI_ORG_ID": "YOUR_ORG_ID",
        "WIKI_READ_ONLY": "true"
      }
    }
  }
}
claude mcp add yandex-wiki-search \
  -e WIKI_TOKEN=YOUR_TOKEN -e WIKI_ORG_ID=YOUR_ORG_ID -e WIKI_READ_ONLY=true \
  -- uvx yandex-wiki-search-mcp
{
  "mcpServers": {
    "yandex-wiki-search": {
      "command": "docker",
      "args": ["run","--rm","-i",
        "-e","WIKI_TOKEN","-e","WIKI_ORG_ID","-e","WIKI_READ_ONLY=true",
        "ghcr.io/dlbolshov/yandex-wiki-search-mcp:latest"],
      "env": {"WIKI_TOKEN":"YOUR_TOKEN","WIKI_ORG_ID":"YOUR_ORG_ID"}
    }
  }
}
TIP

Start withWIKI_READ_ONLY=true — the server won't even register write tools. Flip it to false once you trust your agent with edits.

  1. Ask your agent something — see below.

The server runs on MCP Python SDK v2. That is invisible to clients — one v2 server answers every protocol revision back to 2024-11-05 as well as the current one, so there is nothing to change on your side and nothing to reinstall.

The only reason to hold back is a shared environment that pins mcp<2 for something else. 1.0.1 is the last release built on the 1.x SDK and stays on PyPI:

pip install "yandex-wiki-search-mcp<1.1"

Related MCP server: mediawiki-mcp-server

What can it do

"Find our onboarding docs and summarize the key steps."

"What do we have on incident response? Open the most relevant page."

"Create a page team/weekly-notes and append today's standup summary."

"Add a row to the on-call rotation grid: alice, next week."

"Upload this PDF to the project page and link it at the bottom."

"Delete the draft page, but keep the recovery token in case I change my mind."

Tools

33 tools. All write tools disappear when WIKI_READ_ONLY=true.

Search & read (10)

Tool

What it does

page_search

Full-text search across the entire Wiki (pages and files), ranked results with a text excerpt each; server-side filters, and cursor paging through ~100 results in the highlight mode (up to 50 in one call otherwise)

page_get

Get a page by page_id or slug (accepts full Wiki URLs too)

page_get_descendants

Traverse a page subtree — one flat list of {id, slug} from all nesting levels; from_root=true walks the whole Wiki; fetch_all drains the cursor in one call

page_get_comments

List page comments (fetch_all supported)

page_get_resources

List page resources (attachments + grids) with server-side title search (fetch_all supported)

page_get_attachments

List page attachments (fetch_all supported)

page_read_attachment

Read an attachment's content straight into the conversation (nothing is saved anywhere) — PNG/JPEG/GIF/WebP as a native image block that vision-capable clients render, text as text (SVG included: it is XML, and an image block a vision API cannot decode fails the host's next call), other binaries as a base64 blob. The format is decided by the file's magic bytes, not by the wire's claim. Capped to protect the model's context window: 128 KiB for text/binary, 2 MiB for images; anything larger is refused with a pointer to page_download_attachment or download_url from page_get_attachments

page_get_grids

List grids attached to a page (fetch_all supported)

grid_get

Get a grid by grid_id with row/column/revision filters

user_get_current

Who am I — username and home_cluster (the caller's personal-section slug)

Pages: write (12)

Tool

What it does

page_create

Create a page

page_update

Update page title and/or full content; set or clear a redirect to another page

page_edit

Edit content by exact-text replacements without resending the whole page; a missing or ambiguous match fails the call before anything is written; writes back with allow_merge so a concurrent edit is merged, not overwritten

page_append_content

Append content to top, bottom, or a named anchor

page_clone

Copy a page to a new slug — the copy gets a new id; children, comments, and history stay with the original; occupied slugs are refused. The API has no true move/rename (details)

page_add_comment

Add a comment or reply in a thread

page_delete_comment

Delete a comment; returns the page's updated comment count

page_delete_attachment

Delete an attachment from a page

page_delete

Delete a page and receive a recovery token

page_recover

Recover a deleted page by recovery token

page_upload_attachment

Upload a local file in chunks and attach it to a page — registered only with TRANSPORT=stdio and OAuth off: over HTTP "local" would mean the server's filesystem, not the caller's

page_download_attachment

Download an attachment to a local file — streamed to disk with no size cap, nothing enters the conversation. Written atomically (.part → fsync → rename), refuses to overwrite unless asked, and lands with the permissions a normal write would give (0666 & ~umask, never executable); replacing a file keeps that file's own mode. The directory fsync that makes the rename itself crash-durable, and the mode inheritance, are POSIX-only. Gated the same way as page_upload_attachment: stdio only

Grids: write (11)

Tool

What it does

grid_create

Create a grid on a page

grid_update

Update grid title and/or default sort

grid_copy

Copy a grid to an existing target page (async operation)

grid_delete

Delete a grid

grid_add_rows

Add rows at a position or after a given row

grid_update_cells

Update individual cells by row + column

grid_delete_rows

Delete rows

grid_move_row

Move a row

grid_add_columns

Add typed columns

grid_delete_columns

Delete columns by slug

grid_move_column

Move a column

Grid specifics:

  • Mutations use optimistic locking — fetch the grid first and pass the latest revision.

  • grid_update.default_sort takes [{"column": "status", "direction": "asc"}] entries; the server converts them to the wire format the API expects.

  • grid_add_columns requires required on every column because the real API validates it.

  • grid_copy returns operation metadata, not a ready copied grid object.

How it compares

Facts verified against the alternatives' docs and published code, July–August 2026; the official hosted server's tool list captured live from mcp.wiki.yandex.net (wiki-mcp-server 1.28.1, 2026-08-11).

yandex-wiki-search-mcp

Yandex's official MCP (hosted)

ya-yandex-wiki-mcp

slartus/mcp-yandex-wiki

ya-wiki-mcp

Full-text search

✅ up to 50 results, server-side filters + highlighting

❌ no search tool

❌

✅ up to 10 results

❌

Pages: create / update / append / delete + recover

✅ all, plus partial edits via text replacement (page_edit)

partial — no append / recover; has partial edits via text replacement

✅ all

partial — no append / recover

partial — no recover

Pages: clone to a new slug

✅ page_clone

❌

❌

❌

✅

Grids: write tools

✅ 11

✅ 12, incl. column update + row pin/color

✅ 11

❌ read-only

✅ 11, incl. clone

Comments, attachment upload

✅ incl. deletion, inline image preview, and download to disk

comments ✅ / upload ❌ (download + preview instead)

✅

❌

❌

Server-side read-only mode

✅

❌

✅

❌

❌

Typed output schemas + tool annotations

✅

❌

❌

❌

❌ tools return plain strings

YFM helpers

✅ syntax cheat sheet resource + yfm_warnings in write tools

❌

❌

❌

✅ Markdown→YFM converter + page-tree cache, prompt templates

Docker / PyPI / MCP Registry

✅ / ✅ / ✅

— hosted service, closed source, nothing to install

✅ / ✅ / ✅

❌ manual install

❌ / ✅ / ❌

Multi-user OAuth for HTTP deployments

✅

❌ per-user token pasted into static headers, no OAuth flow

✅

❌

❌

Also worth knowing:

  • best-doctor/mcp-yandex-wiki (Python) — page create / update plus reads, with a separate -ro read-only entry point; no delete / recover, no grids, no search; PyPI only

  • brekhov-ilya/yandex-wiki-mcp (npm) — pages read / write / move, grids read-only; interactive PKCE token flow with auto-refresh, no full-text search

  • n-r-w/yandex-mcp (Go) — Yandex Tracker + Wiki in one server, read-only by design (5 wiki read tools), no search; auth via IAM tokens from the yc CLI only — Yandex OAuth tokens are not supported

  • bim-ba/ycli (Python) — one toolkit for Tracker + Wiki + Forms: a CLI, a Python SDK, a Claude Code plugin, and an MCP server whose Wiki surface is 42 wiki_* tools (15 read / 27 write, annotated, with a --read-only flag); no full-text search tool, and attachment downloads stay CLI/SDK-only

As of August 2026, full-text search exists only here (up to 50 results) and in slartus (up to 10) — Yandex's own hosted server ships without a search tool — and the combination of search, grid writes, server-side read-only mode, and typed schemas is unique to this project.

This project is a fork of ya-yandex-wiki-mcp and builds on findings from slartus/mcp-yandex-wiki — see Credits.

page_search wraps the POST /v1/search endpoint — the same backend that powers the Wiki web search bar, undocumented until Yandex published its API reference in August 2026. Search first, then open a result with page_get by its slug.

  • Two wire modes. By default: up to 50 results in one call (limit is clamped to 1–50; the API rejects anything else) and no pagination — the response cursors are always null. With highlight=true: pages are hard-capped at 10 results regardless of limit, matches come wrapped in <em>, and cursor (the page number echoed back in next_cursor) walks up to ~100 results. The set ends when results comes back empty or next_cursor is null on a non-empty page — past the end next_cursor keeps counting up over empty pages, so it alone does not mean "more exists".

  • Filters run server-side, before the limit — a filtered search does not lose matches to it: slug_prefix (section filter, deep prefixes like tech-doc/ml are fine), result_type (page/file), authors (page owners by uid/cloud_uid — user_get_current supplies your own, turning "find my pages about X" into two calls), and created_between/modified_between date intervals (both bounds required — the API rejects open ones).

  • Quoted "exact phrase" queries work; page results get absolute https://wiki.yandex.ru/... links, file results get direct download links.

  • content is a ~510-character excerpt, not the page and not a summary: it is cut from wherever the match sits, the query terms need not be inside it, and its line breaks and tabs are the page's own layout (table cells arrive tab-separated) rather than separators between fragments. Pass highlight=true to get matches wrapped in <em> tags. Read the page with page_get before answering from it. Empty for file results.

Traversing the tree

page_get_descendants returns a subtree as one flat list of {id, slug} from every nesting level. Passing from_root=true instead of page_id/slug walks the whole Wiki — the way in when no starting slug is known, so search is not the only entry point. Prefer a section slug when you have one: wikis run to thousands of pages, and fetch_all stops at its ~500-item cap with truncated: true.

More verified API behavior (scopes, 403 semantics, error envelopes, limits): docs/api-notes.md.

Configuration

Variable

Required

Default

Description

WIKI_TOKEN

one of the two

—

Yandex OAuth token (takes precedence when both are set)

WIKI_IAM_TOKEN

—

IAM token (Yandex Cloud organizations)

WIKI_ORG_ID

exactly one of the two

—

Yandex 360 organization ID (X-Org-Id)

WIKI_CLOUD_ORG_ID

—

Yandex Cloud organization ID (X-Cloud-Org-Id)

WIKI_READ_ONLY

no

false

true disables all write tools server-side

TRANSPORT

no

stdio

stdio | sse | streamable-http

HOST / PORT

no

127.0.0.1 / 8000

HTTP transports only. The Docker image sets HOST=0.0.0.0, the address a published port reaches; natively, set it only to serve other machines

MCP_ALLOWED_HOSTS

no

loopback without OAuth

HTTP transports only: comma-separated Host names the MCP endpoint answers, each with or without a port (wiki.example.com,mcp-wiki:8000). Unset, a server without OAuth answers only localhost, 127.0.0.1 and [::1], which keeps a web page from driving it through DNS rebinding; list any other name clients use — a Compose service name, a LAN address, a reverse proxy's hostname — or they get 421. A list replaces the loopback default, so keep localhost and 127.0.0.1 in it if local clients still connect. Under OAuth nothing is checked unless this is set. * switches the check off

STATELESS_HTTP / JSON_RESPONSE

no

true / true

streamable-http only: keep no per-session state / answer with JSON instead of SSE

LOG_LEVEL

no

INFO

Logs go to stderr; DEBUG additionally logs Wiki API requests (method, path, status, duration — never headers or bodies)

WIKI_API_BASE_URL

no

https://api.wiki.yandex.net

Wiki API endpoint

WIKI_WEB_BASE_URL

no

https://wiki.yandex.ru

Base for absolute page links in page_search results

WIKI_AUTH_SCHEME

no

OAuth

Authorization header scheme for WIKI_TOKEN (OAuth | Bearer)

WIKI_MAX_RETRIES

no

2

Retries for dropped connections and 429/502/503/504 on requests safe to repeat — GETs (except attachment downloads), search, and upload parts; never timeouts. 0 disables them. A write refused with 429 is not retried: the error says it was not applied and can be resent

TOOL_RESULT_TEXT

no

pretty

Text duplicate of structured tool results: pretty (indent=2) | compact (single line, 10-30% off the text block) | none (structured only — check your client renders structuredContent first)

With OAUTH_ENABLED=true the server becomes an OAuth provider: each MCP user authorizes with their own Yandex account, and requests to the Wiki API are made with their personal token. page_upload_attachment and page_download_attachment are not registered in this mode — nor on any HTTP transport: they read and write files on the machine the server runs on, which over HTTP is not the caller's machine.

Variable

Default

Description

OAUTH_ENABLED

false

Enable the OAuth provider

OAUTH_STORE

memory

memory | redis

OAUTH_SERVER_URL

https://oauth.yandex.ru

Yandex OAuth server

OAUTH_USE_SCOPES

true

Request Wiki scopes during authorization

OAUTH_CLIENT_ID / OAUTH_CLIENT_SECRET

—

Your Yandex OAuth app credentials

OAUTH_REGISTRATION_IDLE_SECONDS

2592000 (30 days)

How long a dynamically registered MCP client is kept unused. Registration is unauthenticated by protocol design, so without an expiry every registration is kept forever. A registration nobody signs in with is dropped this long after registering; each sign-in or token refresh restarts the window, counted from the moment the tokens it issued run out: the 31-day refresh token, or the access token if Yandex issued a longer one (commonly a year). Client secrets never expire on their own (client_secret_expires_at: 0). A client that comes back after its registration is gone has to register again: clients on the TypeScript MCP SDK, mcp-remote among them, do that themselves; the MCP Python SDK client does not, and needs its stored client information cleared. Empty disables the expiry; a registration kept with one while it was on loses it at its next sign-in or refresh. Formerly OAUTH_CLIENT_SECRET_EXPIRY_SECONDS, which is still read

MCP_SERVER_PUBLIC_URL

—

Public URL of this server (OAuth callbacks)

OAUTH_ENCRYPTION_KEYS

—

Comma-separated base64 32-byte keys (required for redis store)

REDIS_ENDPOINT / REDIS_PORT / REDIS_DB / REDIS_PASSWORD / REDIS_POOL_MAX_SIZE

localhost / 6379 / 0 / — / 10

Redis connection

Choosing the organization per user. WIKI_ORG_ID / WIKI_CLOUD_ORG_ID are optional under OAuth, because each request can name its own organization: append ?orgId=... (or ?cloudOrgId=...) to the MCP server URL your client connects to. A query parameter wins over the server-wide setting, so one deployment can serve several organizations. If a request carries neither, the tool call fails with a message pointing at both options — set the environment variable as the default if all your users share one organization.

See .env.example for the full annotated list and compose.yaml for a Redis baseline.

Deployment

%%{init: {"flowchart": {"wrappingWidth": 300}}}%%
flowchart LR
    L["Local MCP client&lt;br/&gt;Claude / Cursor /&lt;br/&gt;Windsurf / VS Code&lt;br/&gt;single user"]
    T["Team MCP clients&lt;br/&gt;multi-user,&lt;br/&gt;optional OAuth"]
    S["yandex-wiki-search-mcp"]
    W["Yandex Wiki API"]
    R[("Redis&lt;br/&gt;optional OAuth&lt;br/&gt;token store")]
    L -- "stdio" --> S
    T -- "streamable-http" --> S
    S --> W
    S -.-> R

HTTP server via Docker (the MCP endpoint is http://localhost:8000/mcp):

docker run --env-file .env -e TRANSPORT=streamable-http -p 127.0.0.1:8000:8000 \
  --log-opt max-size=10m --log-opt max-file=3 \
  ghcr.io/dlbolshov/yandex-wiki-search-mcp:latest
WARNING

WithoutOAUTH_ENABLED=true the HTTP endpoint has no authentication of its own: anyone who can reach the port works with your WIKI_TOKEN. The examples publish it on loopback only, which keeps other machines out, and the server answers only loopback Host names, which keeps out a web page that rebinds its own name to 127.0.0.1 (see MCP_ALLOWED_HOSTS). Neither is authentication: any process on the machine can still use it. Widen access only behind an authenticating reverse proxy, or with OAuth on.

NOTE

The server writes no log files of its own — everything goes to stderr, which Docker's defaultjson-file driver stores without a size limit. The --log-opt flags above cap it; drop them only if your daemon already sets a default.

services:
  mcp-wiki:
    image: ghcr.io/dlbolshov/yandex-wiki-search-mcp:latest  # or: build: .
    ports:
      - "127.0.0.1:8000:8000"
    environment:
      - WIKI_TOKEN=${WIKI_TOKEN}
      - WIKI_ORG_ID=${WIKI_ORG_ID}
      - TRANSPORT=streamable-http
      # Only if another container reaches it as http://mcp-wiki:8000:
      # - MCP_ALLOWED_HOSTS=localhost,127.0.0.1,mcp-wiki
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"

For Redis-backed OAuth storage, use the existing compose.yaml as the baseline.

Security

  • Read-only is server-side: with WIKI_READ_ONLY=true write tools are never registered — there is nothing for a confused agent to call.

  • Plain-token HTTP is unauthenticated: with an HTTP transport and OAuth off, every caller that reaches the port acts as the owner of WIKI_TOKEN — in any organization that token can reach, since ?orgId=/?cloudOrgId= on the endpoint override the configured one. Keep it on loopback or behind an authenticating proxy, or enable OAuth. Loopback alone does not keep out a web page that rebinds its own name to 127.0.0.1, so the server also answers only the Host names in MCP_ALLOWED_HOSTS — loopback ones by default. The local-filesystem tools (page_upload_attachment, page_download_attachment) are registered over stdio only, so an HTTP server never reads or writes its own disk on a caller's behalf.

  • Wiki API does not enforce OAuth scopes (re-verified 2026-08-11, after Yandex documented the scopes — see docs/api-notes.md): a wiki:read token can still write, so use the read-only mode rather than relying on token scopes.

  • Secrets are SecretStr throughout — masked in logs and repr; DEBUG HTTP logging never includes headers or bodies.

  • Deletion is recoverable: page_delete returns a recovery token for page_recover.

  • Unrelated keys in a shared .env are ignored, but a misspelled setting (WIKI_READ_ONL) stops the server instead of silently falling back to a default you did not choose.

Development

uv sync --dev
uv run yandex-wiki-search-mcp   # run locally
uv run pytest                   # tests

uv picks an interpreter from Python 3.11–3.14, the range uv.lock has wheels for (.python-versions), and downloads one if the machine has none.

Before committing, run the full verification set from CONTRIBUTING.md. How the server is put together — the layers, the code map, testing seams, CI and the release process — is described in docs/architecture.md. Verified API behavior and probe scripts are documented in docs/api-notes.md.

The Wiki API drifts (the search endpoint silently changed contract once already, back when it was undocumented) — scripts/contract_sweep.py re-verifies every client method against a live organization and reports validation mismatches and undeclared keys:

uv run python scripts/contract_sweep.py users/YOU/contract-sweep            # live contract checks
uv run python scripts/contract_sweep.py users/YOU/contract-sweep --cleanup  # remove fixtures

With SWEEP_SLUG=users/YOU/contract-sweep in .env (see .env.example) the slug argument can be omitted; the server itself never reads that variable.

The API drift check workflow runs the same sweep weekly when the DRIFT_* repository secrets are configured (instructions in the workflow header); without them it skips quietly.

Credits

This project began as a fork of APonkratov/yandex-wiki-mcp (ya-yandex-wiki-mcp) by Aleksandr Ponkratov, an excellent, well-tested Python MCP server for the Yandex Wiki API, licensed under Apache-2.0. It has since grown its own surface — full-text search, typed input schemas on all 33 tools and output schemas on 32, YFM helpers, cursor draining, multi-user OAuth and a live contract sweep against the API — while the original copyright and license are preserved (see LICENSE and NOTICE).

The idea and key API findings behind full-text search come from slartus/mcp-yandex-wiki (JavaScript, MIT): it was the first to discover the then-undocumented POST /v1/search endpoint (Yandex published a reference for it only in August 2026) and to report that OAuth scopes are not enforced. No code was taken from it — only findings and ideas, independently re-verified against a live organization and extended here.

Trademarks

"Yandex" and "Yandex Wiki" are trademarks of YANDEX LLC. This is an unofficial, community-built project: not affiliated with, sponsored, or endorsed by Yandex — the names are used nominatively, to state which service the server talks to. The logo is an original mark that reproduces neither Yandex Wiki nor MCP branding (design notes).


mcp-name: io.github.dlbolshov/yandex-wiki-search-mcp

Available Tools

33 tools
grid_add_columnsAdd Wiki Grid ColumnsA

Add columns to a Yandex Wiki dynamic table. Fetch the grid first and pass the latest revision. This changes structured data.

Inputs: columns (required), grid_id (required), revision (required), position. Returns: Row and column mutations answer with `results` (+ `revision`).

grid_add_rowsAdd Wiki Grid RowsA

Add rows to a Yandex Wiki dynamic table. Fetch the grid first and pass the latest revision. This changes structured data.

Inputs: rows (required), grid_id (required), revision (required), position, +1 more. Returns: Row and column mutations answer with `results` (+ `revision`).

grid_copyCopy Wiki GridA

Copy a Yandex Wiki dynamic table to an existing target page. This starts an asynchronous operation and returns operation metadata.

Inputs: grid_id (required), slug, title, page_id. Returns: dry_run, operation, status_url

grid_createCreate Wiki GridA

Create a Yandex Wiki dynamic table resource on a page. This changes structured data.

Inputs: title (required), slug, page_id. Returns: id, page, rows, title, +7 more

grid_deleteDelete Wiki GridB
Destructive

Delete a Yandex Wiki dynamic table. This changes structured data and is destructive.

Inputs: grid_id (required). Returns: Acknowledgment for `DELETE /grids/{id}`. The endpoint answers 204 No Content (d…

grid_delete_columnsDelete Wiki Grid ColumnsA
Destructive

Delete columns from a Yandex Wiki dynamic table. Fetch the grid first and pass the latest revision. This changes structured data.

Inputs: grid_id (required), revision (required), column_slugs (required). Returns: Row and column mutations answer with `results` (+ `revision`).

grid_delete_rowsDelete Wiki Grid RowsA
Destructive

Delete rows from a Yandex Wiki dynamic table. Fetch the grid first and pass the latest revision. This changes structured data.

Inputs: grid_id (required), row_ids (required), revision (required). Returns: Row and column mutations answer with `results` (+ `revision`).

grid_getGet Wiki GridA
Read-only

Get a Yandex Wiki dynamic table by grid ID.

Inputs: grid_id (required), sort, fields, filter, +3 more. Returns: id, page, rows, title, +7 more

grid_move_columnMove Wiki Grid ColumnA
Idempotent

Move a column inside a Yandex Wiki dynamic table. Fetch the grid first and pass the latest revision. This changes structured data.

Inputs: grid_id (required), position (required), revision (required), column_slug (required). Returns: Row and column mutations answer with `results` (+ `revision`).

grid_move_rowMove Wiki Grid RowA
Idempotent

Move a row inside a Yandex Wiki dynamic table. Fetch the grid first and pass the latest revision. This changes structured data.

Inputs: row_id (required), grid_id (required), revision (required), position, +1 more. Returns: Row and column mutations answer with `results` (+ `revision`).

grid_updateUpdate Wiki GridA
Idempotent

Update a Yandex Wiki dynamic table. Fetch the grid first and pass the latest revision. This changes structured data.

Inputs: grid_id (required), revision (required), title, default_sort. Returns: id, page, rows, title, +7 more

grid_update_cellsUpdate Wiki Grid CellsA
Idempotent

Update cells in a Yandex Wiki dynamic table. This changes structured data. Each cell patch must include row_id, value, and exactly one of column_id or column_slug.

Inputs: cells (required), grid_id (required). Returns: `POST /grids/{id}/cells` answers with `cells`, not `results`. Its own model rat…

page_add_commentAdd Page CommentB

Add a comment to a Yandex Wiki page.

Inputs: body (required), slug, page_id, parent_id, +1 more. Returns: id, body, author, parent_id, +7 more

page_append_contentAppend Wiki ContentA

Append content to the top, bottom, or anchor of a Yandex Wiki page. Content is Markdown (YFM): plain Markdown renders as-is, but GitHub-specific extensions ('[!NOTE]' alerts, raw HTML) do not — see the wiki-mcp://yfm-cheatsheet resource for YFM equivalents.

Inputs: content (required), slug, anchor, page_id, +1 more. Returns: id, slug, owner, title, +10 more

page_cloneClone Wiki PageA

Copy a Yandex Wiki page to a new slug and return the copy's id and slug once the operation completes. Copies title and content only: child pages, comments, attachments, and edit history stay with the original, and the copy gets a new page id. Fails when the target slug is already occupied. The Wiki API has no true move/rename; to relocate a page, clone it and delete the original — re-uploading attachments and re-creating grids on the copy if they must follow.

Inputs: target (required), slug, title, page_id. Returns: The clone operation's result: where the copy landed. `POST /pages/{id}/clone` i…

page_createCreate Wiki PageA

Create a Yandex Wiki page. Content is Markdown (YFM): plain Markdown renders as-is, but GitHub-specific extensions ('[!NOTE]' alerts, raw HTML) do not — see the wiki-mcp://yfm-cheatsheet resource for YFM equivalents.

Inputs: slug (required), title (required), content (required). Returns: id, slug, owner, title, +10 more

page_deleteDelete Wiki PageA
Destructive

Delete a Yandex Wiki page and return a recovery token.

Inputs: slug, page_id. Returns: recovery_token

page_delete_attachmentDelete Page AttachmentA
Destructive

Delete an attachment from a Yandex Wiki page. File ids come from page_get_attachments. Does not touch page content — any file macro referencing the attachment stays behind, broken.

Inputs: file_id (required), slug, page_id. Returns: Acknowledgment for `DELETE /pages/{id}/attachments/{fid}`. The endpoint answers…

page_delete_commentDelete Page CommentA
Destructive

Delete a comment from a Yandex Wiki page and return the page's updated comment count. Comment ids come from page_get_comments.

Inputs: comment_id (required), slug, page_id. Returns: Acknowledgment for `DELETE /pages/{id}/comments/{cid}`. The endpoint answers 20…

page_download_attachmentDownload Page AttachmentA

Download a Yandex Wiki page attachment to a local file: the bytes stream to disk without a size cap and never enter the conversation — the counterpart to page_read_attachment, for getting the artifact itself (a PDF, an archive, a large export). Writes atomically; refuses to replace an existing file unless overwrite is true. File ids come from page_get_attachments.

Inputs: file_id (required), save_to (required), slug, page_id, +1 more. Returns: Acknowledgment for a download-to-disk: where the bytes landed. Built client-sid…

page_editEdit Wiki Page ContentA

Edit a Yandex Wiki page by exact-text replacements, without resending the whole page: reads the current content, applies the replacements in order, and writes the result back with a single update. Each old_text must match the stored YFM markup exactly (copy it from page_get, whitespace included) and occur exactly once unless replace_all is set — a missing or ambiguous match fails the whole call before anything is written. NOTE: the Wiki API has no page revisions, so the read-modify-write is not atomic; allow_merge (on by default) asks Wiki to merge a concurrent edit that landed in between rather than overwrite it. Do NOT blindly retry a call whose result you did not see: a replacement whose new_text contains its own old_text applies again on a repeat. Content is Markdown (YFM): plain Markdown renders as-is, but GitHub-specific extensions ('[!NOTE]' alerts, raw HTML) do not — see the wiki-mcp://yfm-cheatsheet resource for YFM equivalents.

Inputs: replacements (required), slug, page_id, is_silent, +1 more. Returns: Compact acknowledgment for page_edit — also tool-level, never from the wire. De…

page_getGet Wiki PageA
Read-only

Get a Yandex Wiki page by page_id or slug.

Inputs: slug, fields, page_id. Returns: id, slug, owner, title, +9 more

page_get_attachmentsGet Page AttachmentsB
Read-only

Get attachments for a Yandex Wiki page.

Inputs: slug, cursor, page_id, fetch_all, +1 more. Returns: results, truncated, next_cursor, prev_cursor

page_get_commentsGet Page CommentsB
Read-only

Get comments for a Yandex Wiki page.

Inputs: slug, cursor, page_id, fetch_all, +1 more. Returns: results, truncated, next_cursor, prev_cursor

page_get_descendantsGet Page DescendantsA
Read-only

Get the subtree of Yandex Wiki pages under a parent page. Returns descendants from ALL nesting levels as one flat list of {id, slug} items — slugs encode the hierarchy ('/x/y' is nested under '/x'), so the tree can be reconstructed without further calls. Combine with fetch_all=true to map a whole section at once; if the result comes back truncated=true, continue via next_cursor or narrow down by calling this tool on a subsection's slug. Pass from_root=true instead of page_id/slug to enumerate the WHOLE Wiki, top-level pages included — the way to inventory an organization when no starting slug is known. Prefer a section slug when you have one: a full wiki is routinely thousands of pages, so a root walk costs many requests and a large reply, and fetch_all stops at its ~500-item cap with truncated=true.

Inputs: slug, cursor, page_id, fetch_all, +3 more. Returns: results, truncated, next_cursor, prev_cursor

page_get_gridsGet Page GridsA
Read-only

Get dynamic tables attached to a Yandex Wiki page.

Inputs: slug, cursor, page_id, order_by, +3 more. Returns: results, truncated, next_cursor, prev_cursor

page_get_resourcesGet Page ResourcesB
Read-only

Get resources linked to a Yandex Wiki page, including attachments and grids.

Inputs: slug, cursor, search, page_id, +5 more. Returns: results, truncated, next_cursor, prev_cursor

page_read_attachmentRead Page AttachmentA
Read-only

Read a Yandex Wiki page attachment's content into the conversation (nothing is saved anywhere): PNG/JPEG/GIF/WebP images arrive as a native image block — vision-capable clients render and see them — text files (SVG included, it is XML) as text, anything else base64-encoded. Meant for images and text attachments — diagrams, screenshots, configs, CSVs, logs. Refuses non-image content over 128 KiB and images over 2 MiB. Use page_download_attachment to save it locally, or fetch the attachment's download_url from page_get_attachments yourself. page_get_attachments is also where file ids come from.

Inputs: file_id (required), slug, page_id.

page_recoverRecover Wiki PageA

Recover a deleted Yandex Wiki page using a recovery token.

Inputs: recovery_token (required). Returns: id, slug, pages_count

page_updateUpdate Wiki PageA
Idempotent

Update an existing Yandex Wiki page: title, content, or a redirect to another page. Content replacement is full-page when content is provided. Content is Markdown (YFM): plain Markdown renders as-is, but GitHub-specific extensions ('[!NOTE]' alerts, raw HTML) do not — see the wiki-mcp://yfm-cheatsheet resource for YFM equivalents.

Inputs: slug, title, content, page_id, +4 more. Returns: id, slug, owner, title, +10 more

page_upload_attachmentUpload Page AttachmentA

Upload a local file to Yandex Wiki and attach it to a page.

Inputs: file_path (required), slug, page_id, append_markup, +1 more. Returns: page_id, attachments, appended_markup, appended_content

user_get_currentGet Current UserA
Read-only

Get the calling Yandex Wiki user: username, home_cluster (the caller's personal-section slug, e.g. 'users/' — where 'create it in my section' requests belong), and identity/org ids.

Inputs: no named parameters. Returns: org, identity, username, home_cluster

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 33 tools

    Disambiguation4/5

    Most tools target distinct resources or actions, and the detailed descriptions make choices clear. However, page_get_resources overlaps with page_get_attachments and page_get_grids, and grid_update vs grid_update_cells could be confused at first glance.

    Naming Consistency5/5

    All tools follow a consistent resource-prefixed snake_case pattern (page_, grid_, user_) with clear verbs and optional objects. Even related mutations like grid_add_rows, grid_delete_rows, and grid_move_column are predictable.

    Tool Count2/5

    At 33 tools, the surface is well beyond the 16-25 range and feels heavy for an agent to navigate. While the coverage is broad, several operations could likely be consolidated or grouped to reduce cognitive load.

    Completeness5/5

    The server covers the full page lifecycle, search and hierarchy navigation, comments, attachments, and dynamic tables with CRUD and row/column operations. The only gaps (e.g., move/rename) are explicitly acknowledged with documented workarounds, so agents are not left at dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers