Lean YouTrack MCP server with compact tools, correct subtask hierarchy, tags, board/sprint, work-item types, and attachments.
Strong foundation with 18 well-defined tools covering YouTrack operations. All tools have descriptions (avg 180 chars) and input schemas with typed parameters. Naming follows verb_noun convention (issue_write, issue_get, search, etc.). Key strengths: comprehensive parameter descriptions, enum constraints for operation types, clear risk classifications. Weaknesses: output schemas not visible in source (only referenced via api_schema tool); some parameter descriptions lack format/constraint details (e.g., date formats, field value types); error handling guidance sparse; no tool annotations (readOnlyHint/destructiveHint) despite clear read/write distinction.
Get activity (change history) for an issue or user feed. Supports filtering by date range, author, and activity categories.
Dynamically generated API tools from YouTrack OpenAPI specification. Each tool mirrors a YouTrack REST API endpoint with full parameter and response schema support.
Return the full OpenAPI output JSON Schema for a generated api_* operation. Generated output schemas are available on demand instead of being duplicated in tools/list, which keeps MCP discovery below infrastructure payload limits. Input schemas remain attached directly to every generated tool.
Get a single article by id, or search articles by query.
Create or update an article (knowledge base entry). op=update needs id.
Manage attachments: list, get metadata, download, or delete. Supports uploading files from ChatGPT.
Output schemas not documented in tool definitions. Only api_schema tool provides access to generated API output schemas; core tools (issue_write, comment_write, etc.) lack visible return type documentation. LLMs cannot plan downstream operations without knowing response structure.
Tool annotations missing. Tools clearly marked as READ_ONLY or WRITE in metadata, but no readOnlyHint/destructiveHint/idempotentHint annotations in schema. Agents cannot distinguish safe-to-retry operations from irreversible ones without parsing descriptions.
Date/time format constraints not explicit in parameter descriptions. workitems_list accepts 'ISO date YYYY-MM-DD or unix ms' but activity_get uses same phrasing inconsistently. LLMs frequently miscalculate timestamp conversions; explicit format constraints prevent errors.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2025-06-18+ | v2 |
Create or update a comment on an issue or article (entity). op=update needs commentId.
List comments on an issue or article.
Get a single issue by id with full fields.
List links of an issue (direction, type, related issues).
Search issues by YouTrack query. fields short|full.
Create, update or delete an issue: summary, description, parentId (native subtask), assignee (login; null clears), tags (must exist), state, customFields, board/sprint. customFields=[{name,value}] updates any issue custom field: strings/string arrays are shorthand for named single/multi values; null/[] clear; API-native JSON values pass through. Field types are discovered automatically. board+sprint resolve by name or id, any language/casing. op=delete is irreversible.
Add or remove an issue link. role outward|inward for directed types. For parent/child use issue_write.parentId.
Get metadata: projects, link types, or work item types. Optionally filtered by project.
Get user information: list all users, get current user (me), or get a specific user by id/login.
Create, update or delete a work item (time tracking entry). op=delete is irreversible.
List work items (time tracking entries) with optional filtering.
Generate a time tracking report for a date range with expected vs actual hours per day.
Error recovery guidance absent. No tool descriptions explain what to do on failure (e.g., 'If issue not found, try issue_search() first'). Agents lack actionable next steps when calls fail.
api_* tool definitions inferred from OpenAPI spec generation; explicit tool registration not visible in source. Dynamic API tool schema completeness cannot be verified from static code.