Yandex Tracker MCP
by elicad-keyns
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_API_KEY | Yes | API key for protecting the MCP endpoint | |
| YANDEX_ORG_ID | Yes | Organization ID from Yandex Tracker | |
| MCP_PUBLIC_URL | No | Public URL of the MCP server (e.g., https://tracker-mcp.example.com) | |
| TRACKER_BACKEND | No | Backend type: 'yandex' or 'mock' | yandex |
| YANDEX_AUTH_TYPE | No | Authentication type, typically 'oauth' | oauth |
| YANDEX_CLIENT_ID | No | Client ID for generating OAuth URL (only needed for auth setup) | |
| YANDEX_ORG_HEADER | No | Header for organization ID: 'X-Org-ID' for Yandex 360 or 'X-Cloud-Org-ID' for Yandex Cloud | X-Org-ID |
| YANDEX_DEFAULT_QUEUE | Yes | Default queue key (e.g., 'TEST') | |
| YANDEX_TRACKER_TOKEN | Yes | OAuth token for Yandex Tracker (required for production) |
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
ActivityStale
ResponsivenessNo issues