Jira Issue MCP Server
Related Servers
Alternatives to Jira Issue MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication. It enables users to perform CRUD operations on issues, search with JQL, manage comments, and list projects through the Jira REST API.12567 npm16MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to read and create Jira issues against Jira Cloud or Data Center through a self-hosted FastMCP server with secure authentication and configurable fields.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI applications to manage JIRA issues, workflows, and tasks through a standardized MCP interface, facilitating real-time updates and seamless interaction with JIRA's API.10MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to work with a self-hosted Jira Server / Data Center instance through its REST API, covering JQL search, issue creation and updates, comments, workflow transitions, linking, and project/user lookups using a personal access token.MIT
- FlicenseNot gradedqualityDmaintenanceEnables MCP clients to read, create, update, comment on, and transition Jira issues using Jira Cloud's free plan.-
- AlicenseNot gradedqualityDmaintenanceEnables seamless Jira integration through browser-based OAuth authentication, providing tools for issue management, JQL search, and project access without manual API token configuration.2MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: create_issue handles issue creation, get_accessible_resources lists general resources, and get_projects focuses specifically on projects. There is no overlap or ambiguity between these functions.
The naming is mostly consistent with a verb_noun pattern (create_issue, get_projects), but get_accessible_resources uses a more descriptive adjective, slightly deviating from pure verb_noun. Overall, it remains readable and predictable.
With only 3 tools for a Jira server, the count feels too thin for the domain. Jira typically involves CRUD operations on issues, projects, and other resources, so this limited set is insufficient for comprehensive coverage.
The tool surface is significantly incomplete for a Jira server. It includes create_issue but lacks get_issue, update_issue, and delete_issue, and while get_projects is present, other common operations like search_issues or manage_workflows are missing, leading to potential agent failures.