Yandex Tracker MCP Server
Related Servers
Alternatives to Yandex Tracker MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for Yandex Tracker API, enabling AI assistants to search, read, create, and edit issues, as well as manage comments, attachments, and links in Yandex Tracker.48 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA Node.js MCP server that enables AI assistants to interact with Yandex Tracker task management system through a standardized protocol, supporting operations like creating, updating, and searching issues.433 npm3ISC
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that integrates with Atlassian Confluence and Jira, enabling AI assistants to search, create, and update content in these platforms through natural language interactions.1MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server for YouTrack integration, providing a standardized interface for LLMs to interact with YouTrack's issue tracking, agile management, and knowledge base features.1211 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Simple Model Context Protocol server that enables AI assistants to interact with Jira, allowing operations like fetching tickets, adding comments, and updating ticket status.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA comprehensive Model Context Protocol server that provides AI agents with 44 tools to manage JetBrains YouTrack issues, sprints, and projects via the REST API. It supports full YouTrack query language and works with both Cloud and Server instances for complete project management integration.78 npmMIT
TDQS
Scored across 57 tools
Each tool targets a distinct resource and action, with clear descriptions that prevent confusion. Even the overlapping issue_close and issue_execute_transition are clearly distinguished as convenience vs generic transition.
Naming is inconsistent: many tools use resource_action (issue_create, queue_get_metadata) but several use action_resource (get_priorities, get_statuses). Also pluralization varies (boards_list vs board_get, queues_get_all vs queue_get_metadata).
With 57 tools, this is far beyond the typical well-scoped MCP server. While the domain is broad, the granularity is excessive, making it unwieldy.
The tool surface covers most CRUD operations for issues, comments, worklogs, attachments, links, and entities. Minor gaps include no filter deletion, board/sprint creation/update, and limited issue search options.