JIRA MCP Server
Related Servers
Alternatives to JIRA MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceWraps Jira Data Center operations as MCP tools, enabling AI assistants to interact with Jira for project management and issue tracking.28 npmApache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Jira Cloud tickets, including listing, searching, creating, and updating issues through a set of MCP tools.-
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with JIRA through MCP, providing 35 tools for issues, comments, transitions, projects, boards, sprints, epics, links, worklogs, versions, attachments, users, and fields.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI applications to manage JIRA issues, workflows, and tasks through a standardized MCP interface, facilitating real-time updates and seamless interaction with JIRA's API.10MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Jira Cloud by managing issues, comments, custom fields, and sprint tasks through a standardized interface. Supports issue creation, updates, team activity tracking, and progress reporting.1128 npmApache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables to interact with JIRA issues and sprints through MCP tools, including fetching tickets, adding comments, linking issues, and more.530 npm1-
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose targeting specific JIRA operations: creating, retrieving, updating, commenting on, searching for, and transitioning issues. There is no overlap or ambiguity between these functions.
All tools follow a consistent 'jira_verb_noun' pattern with snake_case throughout. The naming is predictable and uniform across all six tools.
Six tools is reasonable for a JIRA server, covering core issue management operations. It's slightly lean but includes essential CRUD and workflow actions, with minor gaps like missing project or user management.
The toolset covers key JIRA workflows: create, read, update, search, comment, and transition issues. Minor gaps exist, such as no delete operation or project-level tools, but agents can handle most common tasks effectively.