A
licenseNot graded
qualityA
maintenanceSupercharge your AI assistant with seamless Jira integration. Enables AI assistants like GitHub Copilot and Claude to interact with your Jira Cloud instance.
281 npm
MIT
Jira MCP Server
by ashu-arora
Related Servers
Alternatives to Jira MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI coding assistants to search, create, update, and manage Jira issues, users, and projects via natural language, using the Jira REST API and MCP stdio transport.408 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables searching, reading, listing, creating, and updating Confluence pages via natural language in GitHub Copilot.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, view, create, and update JIRA issues using natural language commands and JQL queries.60 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceConnects Jira projects to AI assistants, enabling natural language queries to view, search, and filter stories with real-time access to descriptions, comments, status, and metadata without leaving your development environment.60 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables managing Jira tickets via Cursor AI, allowing users to create, search, update, and comment on issues directly from the AI assistant.60 npmApache 2.0
TDQS
A3.8/5.0
Scored across 10 tools
Disambiguation5/5
Each tool has a clear, distinct purpose: search vs. get, create vs. update, comment, transitions, assignment, project listing, and user profile. There is no ambiguity between tools; an agent can reliably select the correct one based on the action needed.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (e.g., search_issues, get_issue, create_issue, add_comment). Even the 'get_*' tools differ by object (issue, transitions, myself), maintaining predictability. No mixed conventions or vague verbs.
Tool Count5/5
With 10 tools, the server is well-scoped for Jira's core functionality. Each tool serves a necessary purpose, covering create, read, update, search, comments, transitions, assignment, and user/project context. No redundancy or bloat.
Completeness4/5
The set covers the primary Jira workflows: issue lifecycle (create, get, update, transition, assign), search, comments, and context (projects, user). Minor gaps exist (e.g., no delete_issue, no link_issue), but these are not critical for most automation tasks and can be worked around.
Maintenance
ActivityMaintained
ResponsivenessNo issues