mcp-yandex360
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YANDEX_ORG_ID | No | Organization id — only `telemost_org_settings` needs it | |
| YANDEX_READ_ONLY | No | Set to '1' to make every mutating tool refuse, with a clear message | |
| YANDEX_DISK_TOKEN | No | OAuth token, scopes `cloud_api:disk.read` / `.write` / `.info` | |
| YANDEX_ALLOW_DELETE | No | Set to '1' to enable delete tools (required on top of write access) | |
| YANDEX_TELEMOST_TOKEN | No | OAuth token, scopes `telemost-api:conferences.create` / `.read` / `.update` | |
| YANDEX_MESSENGER_BOT_TOKEN | No | Bot token from the Yandex 360 admin panel |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivitySlowing
ResponsivenessNo issues