Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DISK_READNoDisk read permissiontrue
WIKI_READNoWiki read permissiontrue
DISK_WRITENoDisk write permissionfalse
WIKI_WRITENoWiki write permissionfalse
DISK_DELETENoDisk delete permissionfalse
WIKI_DELETENoWiki delete permissionfalse
MCP_TRANSPORTNoTransport (stdio recommended for standard MCP clients)stdio
DISK_ALLOWED_ROOTSNoComma-separated allowed roots for Disk/Work,/Research
WIKI_ALLOWED_ROOTSNoComma-separated allowed roots for Wikiprojects,research
YANDEX_OAUTH_TOKENYesOAuth token generated from Yandex OAuth portal
YANDEX_WIKI_ORG_IDNoYour Organization ID (required if Wiki is enabled and you are under an org)
YANDEX_DISK_ENABLEDNoToggle Yandex Disk integrationtrue
YANDEX_WIKI_ENABLEDNoToggle Yandex Wiki integrationtrue

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 8 tools

Disambiguation3/5

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.

Naming Consistency3/5

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.

Tool Count5/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues