yt-mcp
Related Servers
Alternatives to yt-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables interacting with YouTrack through natural language, covering issues, comments, projects, time tracking, agile boards, and more via the YouTrack REST API.13 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for interacting with YouTrack, enabling issue management, project operations, and search via natural language.28 npm98MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for comprehensive YouTrack integration, enabling issue management, work tracking, search, and knowledge base operations.635 npm6MIT
- 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.1213 npmMIT
- 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.20 npm1MIT
- AlicenseAqualityFmaintenanceMCP server for YouGile project management. Provides 57 tools covering 100% of YouGile API v2, enabling natural language management of projects, boards, columns, tasks, chats, users, and more.5744 npm10MIT
TDQS
Scored across 84 tools
The core CRUD tools are distinct, but there are many overlapping analytics/reporting tools: get_top_active_issues vs get_team_dashboard vs get_team_pulse vs get_multi_team_dashboard/pulse, and get_handoff_snapshot vs get_stuck_handoffs vs track_cross_dept_journey vs get_active_sprint_issues. Descriptions do a good job explaining the differences, but an agent still has to read long prose to pick correctly. Some near-duplicates (search_issues vs run_saved_search vs count_issues) add friction.
Almost everything follows snake_case verb_noun (get_issue, create_article, add_comment, delete_work_item). A few minor deviations like get_agiles, poll_changes, and get_my_mentions break the pattern slightly but remain readable and consistent overall.
84 tools is an extreme overload for a single server. Many are highly specialized analytics (deadline_scorecard, audit_deadline_changes, suggest_managers, get_impact_map) that could be consolidated or split into sub-servers, making tool selection costly for an agent.
Coverage is unusually thorough: full CRUD for issues, comments, articles, article comments, work items, attachments, sprints, and boards, plus rollback, bulk operations, and heavy analytics. Minor gaps like no project creation or standalone tag management are easy workarounds.