A
licenseB
qualityD
maintenanceProvides capabilities for searching Jira issues using JQL and retrieving detailed issue information.
2
338 npm
28
MIT
mcp-jira-stdio
by freema
Related Servers
Alternatives to mcp-jira-stdio
- AlicenseAqualityBmaintenanceMCP server for Taskwarrior 3.x — 35 tools for task lifecycle, time tracking, schema validation, and role-based permissions.3577 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.125 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-
- AlicenseAqualityDmaintenanceA 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.13 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.743 npmApache 2.0
TDQS
A4/5.0
Scored across 23 tools
Disambiguation5/5
Each tool has a clearly distinct purpose, targeting different resources (projects, issues, comments, attachments, etc.) with specific actions (get, create, update, delete, search). There is no overlap; even similar tools like jira_get_visible_projects and jira_get_project_info serve different levels of detail.
Naming Consistency5/5
All tools follow a consistent jira_verb_noun pattern in snake_case (e.g., jira_get_issue, jira_create_issue, jira_transition_issue). The verb is always a clear action, and the noun is the resource. No mixing of conventions.
Tool Count4/5
With 23 tools, the count is slightly above the typical well-scoped range (3-15), but it is justified given the breadth of Jira operations covered. The tools are necessary for comprehensive Jira API interaction, and each adds unique functionality.
Completeness4/5
The toolset covers major CRUD operations (create, update, read, delete attachments) and workflow transitions. However, there is no tool to delete an issue or comment, which are notable gaps. Overall, it provides a solid foundation for Jira management.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive