F
licenseNot graded
qualityD
maintenanceEnables AI agents to manage Yandex Tracker tasks with tools for creating, reading, updating, and transitioning issues via a Streamable HTTP endpoint.
-
Yandex Tracker MCP Server
by DChuhin
Related Servers
Alternatives to Yandex Tracker MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceExposes the Yamtrack REST API as tools for LLMs, enabling media tracking and management through natural language.15AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Yandex Tracker through its API for managing tasks, comments, and attachments. It supports issue searching, status transitions, and metadata retrieval for automated project management.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to securely interact with Yandex Tracker, managing issues, queues, comments, worklogs, and search, including attaching files to issues.56Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Yandex.Tracker task management system through MCP protocol. Supports creating and managing issues, searching tasks, handling comments, managing projects and queues, and generating analytics reports.-
- 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.21 npm1MIT
TDQS
A4/5.0
Scored across 21 tools
Disambiguation5/5
Each tool serves a clearly distinct purpose. Checklist operations are separated into add, list, update, delete, and clear. Issue operations are similarly granular. Even similar tools like search_issues and search_issues_scroll are differentiated by scroll capability, leaving no ambiguity.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern using snake_case (e.g., add_checklist_item, list_components, update_issue). The naming is predictable and uniform across the entire set.
Tool Count5/5
With 21 tools, the server covers the typical lifecycle of an issue tracker: CRUD for issues and checklists, search, linking, comments, sprints, components, validation, and Miro sync. The count is well-scoped for the domain without being too sparse or excessive.
Completeness4/5
The tool surface covers most essential operations: issue creation, retrieval, update, checklist management, linking, commenting, validation, and sprint/component listing. Minor gaps exist, such as no tool for deleting an issue or removing a link, but these are not critical dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues