F
licenseA
qualityC
maintenanceEnables AI agents to manage Jira Cloud issues through natural language, including searching, creating, updating, commenting, assigning, and transitioning issues.
10
-
Jira Extended MCP Server
by Juhwan01
Related Servers
Alternatives to Jira Extended MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to manage Jira projects, issues, sprints, and boards via natural language.60 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jira Cloud issues, supporting create, read, update, delete, search, and transition operations via natural language.9 npmMIT
- AlicenseBqualityCmaintenanceEnables AI agents to manage Jira projects and issues using natural language, including creating, updating, searching issues, managing sprints, and more via the Jira API.3660 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Jira Cloud and Confluence through natural language, performing JQL searches, issue management, and Confluence page creation.104 npm1MIT
- 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-
TDQS
B3.3/5.0
Scored across 27 tools
Disambiguation5/5
Each tool targets a distinct Jira resource or action; single vs. bulk variants (create_issue vs. create_issues_bulk, transition_issue vs. bulk_transition) are clearly distinguished by descriptions. No meaningful overlap would cause misselection.
Naming Consistency4/5
Names are consistently snake_case and mostly follow a verb_noun pattern. Minor deviations exist: bulk_transition uses a prefix while create_issues_bulk uses a suffix, and get_createmeta compresses a Jira term, but the set remains predictable.
Tool Count3/5
27 tools is heavy for an MCP server and exceeds the typical 3-15 range. However, the breadth is aligned with an 'extended' Jira surface covering issues, versions, sprints, comments, worklogs, projects, and boards, so it is over-scoped rather than redundant.
Completeness4/5
Core issue lifecycle is well covered (CRUD, search, transitions, bulk operations, links), and versions have full CRUD. Gaps remain in secondary areas: comments only support add/get, worklogs only support add, and sprints/boards lack full lifecycle management.
Maintenance
ActivityInactive
ResponsivenessNo issues