yandex-workspace-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISK_READ | No | Disk read permission | true |
| WIKI_READ | No | Wiki read permission | true |
| DISK_WRITE | No | Disk write permission | false |
| WIKI_WRITE | No | Wiki write permission | false |
| DISK_DELETE | No | Disk delete permission | false |
| WIKI_DELETE | No | Wiki delete permission | false |
| MCP_TRANSPORT | No | Transport (stdio recommended for standard MCP clients) | stdio |
| DISK_ALLOWED_ROOTS | No | Comma-separated allowed roots for Disk | /Work,/Research |
| WIKI_ALLOWED_ROOTS | No | Comma-separated allowed roots for Wiki | projects,research |
| YANDEX_OAUTH_TOKEN | Yes | OAuth token generated from Yandex OAuth portal | |
| YANDEX_WIKI_ORG_ID | No | Your Organization ID (required if Wiki is enabled and you are under an org) | |
| YANDEX_DISK_ENABLED | No | Toggle Yandex Disk integration | true |
| YANDEX_WIKI_ENABLED | No | Toggle Yandex Wiki integration | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Search across Yandex Disk and Yandex Wiki |
| fetchC | Fetch a canonical resource by ID from Yandex Workspace |
| disk_listB | List contents of a folder on Yandex Disk |
| disk_get_metadataB | Get metadata for a file or folder on Yandex Disk |
| disk_readA | Read text content of a file on Yandex Disk |
| wiki_searchC | Search Yandex Wiki pages |
| wiki_get_pageA | Get a Yandex Wiki page by slug |
| wiki_get_treeA | Get the tree of pages under a Wiki slug |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Search and wiki_search overlap, with wiki_search being a subset of the generic search. Fetch could be confused with the specific getters (disk_get_metadata, wiki_get_page), though its ID-based approach differs slightly. Other tools are clearly distinct.
The disk_* and wiki_* prefixes create a consistent sub-pattern, but generic tools like search and fetch break the pattern. Naming is readable and mostly predictable, but not fully uniform.
With 8 tools covering two domains (Disk and Wiki), the count is well-scoped and appropriate for the server's purpose. Every tool has a clear role, and the number is within the ideal 3-15 range.
The tools cover search, reading, and retrieval well, but lack any write operations (create, update, delete) for both Disk and Wiki. This is a notable gap if the workspace is meant for more than read-only access, though it may be intentional for a search-focused MCP.