A
licenseA
qualityB
maintenanceEnables reading, creating, updating, and appending content to Yandex Wiki pages via MCP. Supports both read-write and read-only modes.
7
9
MIT
yandex-wiki-search-mcp
by dlbolshov
Related Servers
Alternatives to yandex-wiki-search-mcp
- AlicenseNot gradedqualityCmaintenanceMinimal MCP server for Yandex Wiki that enables reading, writing, searching, and managing wiki pages and attachments.1MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI assistants to interact with Yandex 360 organization services, currently supporting Yandex Wiki for reading, editing, and searching pages.MIT
- AlicenseBqualityBmaintenanceProduction-ready MCP server integrating AI assistants with Yandex Disk and Yandex Wiki, offering unified search, file/page management, and security-first access controls.8MIT
- AlicenseAqualityAmaintenanceMCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.4320MIT
- AlicenseBqualityBmaintenanceA secure MCP server for interacting with MediaWiki instances, allowing users to search, read, create, and manage wiki content like pages, categories, and files. It supports both public and private wikis with comprehensive authentication for full read and write operations.19AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceAn MCP server for Wiki.js projects that enables full-text search, page retrieval, and page management capabilities. It allows LLMs to interact with wiki content through specialized tools for searching, listing, and creating pages.-
- FlicenseNot gradedqualityBmaintenanceMCP server for Wiki.js integration, enabling page CRUD operations (create, update, get, list, search, delete, move) via the Wiki.js GraphQL API.-
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
ActivityMaintained
ResponsivenessNo issues