A
licenseB
qualityD
maintenanceProvides capabilities for searching Jira issues using JQL and retrieving detailed issue information.
2
380 npm
28
MIT
mcp-jira-stdio
by freema
Related Servers
Alternatives to mcp-jira-stdio
- AlicenseAqualityCmaintenanceMCP server for Taskwarrior 3.x — 35 tools for task lifecycle, time tracking, schema validation, and role-based permissions.3526 PyPI3Apache 2.0
Related Servers
- AlicenseAqualityBmaintenanceMCP server enabling AI assistants to interact with Jira, scoped to a single project. Supports stdio and HTTP transports for issue management operations.127 npmISC
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables interaction with JIRA APIs through Claude Desktop, allowing users to search, create, update, and manage JIRA issues using natural language commands.1-
- AlicenseAqualityFmaintenanceA Model Context Protocol server that enables interaction with Jira's REST API using natural language commands, allowing users to manage Jira projects, issues, comments, and workflows through Claude Desktop and other MCP clients.107MIT
- FlicenseAqualityCmaintenanceMCP server for logging and checking Jira Cloud worklogs from AI agents such as Claude Code, Claude Desktop, Cursor, or any MCP client that supports stdio.71-
- AlicenseNot gradedqualityCmaintenanceMCP server that wraps the jira-cli command-line tool to enable AI assistants to interact with Jira.17 npm9MIT
- AlicenseBqualityCmaintenanceStdio-based MCP server exposing Jira tools for searching, creating, getting, commenting on, assigning, and transitioning issues, as well as listing projects, with authentication via token or basic auth.748 npmApache 2.0
TDQS
A3.9/5.0
Scored across 23 tools
Disambiguation4/5
Most tools target distinct resources and actions, and descriptions clarify boundaries (e.g., get_visible_projects vs get_project_info). However, minor overlaps exist: jira_get_my_issues could be achieved via jira_search_issues with assignee=currentUser(), and jira_get_issue_types vs jira_get_create_meta both relate to issue type discovery for creation.
Naming Consistency5/5
All tools follow a consistent jira_<verb>_<noun> snake_case pattern, with clear verbs like get, create, update, add, delete, search, and transition. Minor variations like get_visible_projects and get_my_issues remain predictable and readable.
Tool Count3/5
With 23 tools, the set is on the heavy side for a single MCP server, though Jira's complexity justifies many of them. The count falls into the borderline-heavy range (16-25) where consolidation or grouping could improve usability.
Completeness4/5
The surface covers core Jira issue lifecycle: create, read, update, search, comment, attach, link, subtask, transition, and relationship graphing. Gaps remain, such as no jira_delete_issue, no update/delete for comments, and no worklog operations, but these are minor and agents can often work around them.
Maintenance
ActivityActive
ResponsivenessUnresponsive