jira-mcp-server
Related Servers
Alternatives to jira-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for Jira integration with stdio transport. Enables reading, writing, and managing Jira issues and projects directly from Claude Desktop. Supports issue creation, updates, comments, JQL search, and project management.23599 npm14MIT
- FlicenseBqualityBmaintenanceSmall MCP server for connecting to enterprise Jira using a personal access token. It enables issue operations, project listing, JQL searches, and attachment handling.17-
- 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
- AlicenseNot gradedqualityCmaintenanceMCP server that wraps the jira-cli command-line tool to enable AI assistants to interact with Jira.18 npm9MIT
- AlicenseNot gradedqualityCmaintenanceA lightweight MCP server that exposes Jira issue operations (get, search, create) as tools for AI clients like Claude.60 npmISC
- AlicenseNot gradedqualityCmaintenanceA lightweight MCP server for self-hosted Jira Server, exposing REST API v2 tools for search, issue creation/update, transitions, comments, and more to AI clients via MCP protocol.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct Jira operation: search, retrieve, create, comment, assign, transition, and list projects. There is no overlap or ambiguity between them.
All tools share the 'jira_' prefix and use snake_case, with most following a verb_noun pattern (e.g., jira_get_issue). The exception is jira_projects, which is a simple noun rather than 'list_projects', but this is a minor deviation.
With 7 tools, the server is well-scoped for common Jira operations. Each tool covers a core feature without unnecessary bloat or missing essentials.
The set covers create, read, search, comment, assign, and transition, but lacks an update operation (e.g., jira_update_issue), which is a core part of issue lifecycle management. This is a notable gap that agents may need to work around.