yandex-tracker-mcp-lite
Related Servers
Alternatives to yandex-tracker-mcp-lite
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to securely interact with Yandex Tracker, covering queues, issues, comments, worklogs, checklists, boards, sprints, attachments, and advanced query-language search. Supports OAuth 2.0 or static token authentication, optional Redis caching, and stdio, SSE, or HTTP transports.Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to securely interact with Yandex Tracker, managing issues, queues, comments, worklogs, and search, including attaching files to issues.561Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Yandex Tracker tasks with tools for creating, reading, updating, and transitioning issues via a Streamable HTTP endpoint.-
- AlicenseNot gradedqualityCmaintenanceEnables read-only MCP access to Yandex Tracker for retrieving issues with comments and attachment metadata, searching issues, reading issue history, downloading attachments, and finding users. It also supports connection status checks and token configuration without exposing secrets.46 npmMIT
- AlicenseCqualityBmaintenanceEnables AI assistants to work with Yandex Tracker through its API, letting them search, create, edit, close, and bulk-manage issues, comments, checklists, time entries, attachments, queues, boards, dashboards, projects, and automation workflows. It also supports read-only mode for safe viewing integrations.18781 npm1MIT
TDQS
Scored across 9 tools
Each tool targets a distinct action on the issue domain (search, get, create, update, transition, comment, link), and the descriptions explicitly route status changes to transition_issue rather than update_issue, which removes the most likely confusion. The only overlap is call_api, a deliberate catch-all that can duplicate any of the others, but it is clearly framed as a fallback for uncovered resources.
All names are snake_case with a predictable verb_noun shape (add_comment, search_issues, get_issue, transition_issue, update_issue, create_issue, link_issues, call_api). The only deviation is whoami, which is a well-known idiom rather than a verb_noun construction.
Nine tools is well within the sweet spot and each one covers a distinct operation in the issue workflow, with no filler. The 'lite' scope is matched by the surface rather than padded with redundant variants.
Core lifecycle is covered: create, read, update, search, transition, comment, link, plus identity check. Gaps exist (no delete_issue, no comment edit/delete, no attachment upload, worklogs/boards/sprints only via call_api), but the call_api escape hatch makes these workable rather than dead ends.