MCP Issue Tracker
Related Servers
Alternatives to MCP Issue Tracker
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI clients to interact with a mock JIRA-shaped issue tracker through MCP tools for managing projects, issues, and users.-
- AlicenseNot gradedqualityDmaintenanceMCP 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.4 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage GitHub issues by listing, creating, searching, and commenting on them through MCP.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables one developer and their AI agents to manage issues, projects, milestones, labels, sub-issues, priorities, estimates, blockers, attachments, search, and soft delete/restore over MCP, with every write attributed.1 npmMIT
- AlicenseBqualityDmaintenanceProvides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools.68 npm3MIT
- FlicenseAqualityDmaintenanceEnables to interact with Redmine issues through the MCP protocol, allowing operations like get, list, create, and update tickets.41 npm-
TDQS
Scored across 6 tools
Each tool has a clear and distinct purpose: ping for health, and the remaining five tools map cleanly to list/get/create/update/delete operations on issues. There is no overlap or likely misselection between tools.
All issue-specific tools follow a consistent verb_noun pattern (list_issues, get_issue, delete_issue, create_issue, update_issue). The only exception is ping, which is a conventional standalone health-check name and does not undermine the pattern.
With 6 tools, the set is well-scoped for a small issue tracker MCP server. Every tool earns its place: five cover the issue lifecycle and one verifies server availability.
The tool surface provides full CRUD coverage for issues, including listing, retrieving, creating, updating, and deleting. No core lifecycle operation is missing for the stated purpose.