Full-text search across the entire Yandex Wiki. Returns up to 50 results (pages and files) ranked by relevance, each with a title, slug, url, and a text excerpt in content (there is no deeper pagination). Use this to DISCOVER pages, then call page_get with a result's slug to read full content. content is an excerpt of at most ~510 characters cut from wherever the match sits in the page — not the page and not a summary of it, with no highlighting and no guarantee the query terms are even inside it — so treat it as a relevance signal and read the page before answering from it. Wrap multi-word exact phrases in double quotes. Search is global: there is no server-side section filter. slug_prefix and result_type are applied client-side AFTER fetching, so combine them with limit=50 to avoid missing matches. To enumerate a section (or the whole Wiki) rather than search it, use page_get_descendants.

Get a Yandex Wiki page by page_id or slug.

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.

Get comments for a Yandex Wiki page.

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

Get dynamic tables attached to a Yandex Wiki page.

Get a Yandex Wiki dynamic table by grid ID.

Get attachments for a Yandex Wiki page.

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

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

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

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

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

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.

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

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

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

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

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

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.

Update an existing Yandex Wiki 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.

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.

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.

Add a comment to a Yandex Wiki page.

Delete a Yandex Wiki page and return a recovery token.

Recover a deleted Yandex Wiki page using a recovery token.

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