YouTrack MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Optional: Cache TTL in milliseconds (default: 300000 = 5 minutes) | 300000 |
| LOG_LEVEL | No | Optional: Log level (error, warn, info, debug) | info |
| PROJECT_ID | No | Optional: Default project ID | |
| WEBHOOK_PORT | No | Optional: Webhook server port (default: 3000) | 3000 |
| YOUTRACK_URL | Yes | YouTrack instance URL (without trailing slash) | |
| CACHE_ENABLED | No | Optional: Enable cache (true/false, default: true) | true |
| WEBHOOK_SECRET | No | Optional: Webhook secret for signature verification | |
| YOUTRACK_TOKEN | Yes | YouTrack permanent token | |
| ENABLE_WEBHOOKS | No | Optional: Enable webhooks (true/false) | false |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| projectsB | Project management: list projects, get details, validate access, list custom fields, retrieve statistics |
| issuesC | Issue lifecycle: create, update, query/search, change state, comment, start/complete work |
| queryC | Raw YouTrack query using native syntax (returns issues matching the expression) |
| commentsC | Issue comments: list, add, update, delete |
| agile_boardsC | Agile boards and sprints: list boards/sprints, get details, create sprints, assign issues |
| knowledge_baseC | Knowledge base: list, get, create, update, delete, search articles |
| analyticsC | Analytics and reporting: project statistics, time tracking, Gantt, critical path, resource allocation, milestone progress |
| adminC | Administrative operations: search users, inspect fields, list field values, bulk update, create dependencies |
| time_trackingC | Time tracking & work items: log time, manage entries and work items, generate reports |
| authB | Authentication: status, OAuth2 login, logout, re-authenticate, validate token |
| notificationsC | Notifications: status, list, clear, subscribe/unsubscribe, list subscriptions |
| subscriptionsC | Notification subscriptions: create, update, delete, list |
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 12 tools
Each tool is grouped by clear domain (e.g., issues, agile_boards, comments) with distinct responsibilities. Overlaps like issues and query are resolved by raw query being a specialized search tool, while notifications and subscriptions are differentiated by subscription management being a subset of notifications.
All tool names follow a consistent lowercase underscore pattern (e.g., agile_boards, time_tracking). The naming is predictable and uses nouns or adjective_noun combinations, making it easy for an agent to infer functionality.
With 12 tools covering core project management domains (issues, boards, analytics, etc.), the count is well-scoped. Each tool serves a necessary purpose without unnecessary bloat or missing critical features.
The tool set provides comprehensive lifecycle coverage: issue CRUD, state transitions, comments, time tracking, project management, agile boards, knowledge base, notifications, subscriptions, analytics, and admin operations. No obvious dead ends or missing operations for a project management system.