A
licenseNot graded
qualityC
maintenanceProvides Jira and Confluence integration for AI assistants, enabling natural language management of issues, projects, sprints, pages, comments, attachments, and more with 72 tools.
MIT
jira-service-desk-mcp
by CzSadykov
Related Servers
Alternatives to jira-service-desk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityNot gradedmaintenanceEnables AI assistants to interact with Atlassian Jira Cloud, allowing users to manage projects, issues, comments, and workflows through natural language commands.660 npm3-
- AlicenseCqualityDmaintenanceEnables AI assistants to manage Jira Cloud projects, issues, sprints, and more through a curated set of 62 tools covering the full lifecycle of stories, epics, bugs, and sprints.62GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jira Cloud and Server/Data Center deployments for issue management, project tracking, and workflow automation. Supports multiple authentication methods including API tokens, OAuth 2.0, and personal access tokens.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Atlassian Jira via API token authentication, with 46 optimized tools across modular architecture for CRUD, agile, dashboard, and search operations.37 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to interact with Jira Cloud, including listing boards and issues, adding comments, and searching users.739 npm2MIT
TDQS
A3.8/5.0
Scored across 40 tools
Disambiguation5/5
Each tool targets a distinct resource and action (e.g., add vs remove, customer vs organization), and even similar resources like comments have separate create/get/list tools. There is no confusion between tool purposes.
Naming Consistency5/5
Tool names consistently follow the verb_noun pattern in snake_case (e.g., list_service_desks, add_customers_to_service_desk). Minor deviations like get_service_desk_info are rare and do not break the pattern.
Tool Count4/5
40 tools cover a broad domain (desks, organizations, customers, requests, comments, approvals, queues, transitions, attachments). While slightly heavy, each tool serves a distinct purpose and the count is justified for the complexity of Jira Service Management.
Completeness3/5
Core CRUD and lifecycle operations are present for requests, comments, attachments, and organizations, but notable gaps exist: no update/delete for customers, no update for organizations, and no direct tool to update request fields (only transitions).
Maintenance
ActivityInactive
ResponsivenessNo issues