mcp-server-jira
Related Servers
Alternatives to mcp-server-jira
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for interacting with Jira Cloud, providing tools for issues, search, agile boards, comments, links, attachments, and webhook notifications.7 npm2MIT
- AlicenseAqualityBmaintenanceMCP server for Jira Server/Data Center that enables issue retrieval, JQL search, comment posting, and Tempo worklog queries via the atlassian-python-api.19MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for interacting with Jira Cloud instances. Enables issue management, JQL queries, project and sprint management, and batch operations via natural language interfaces.206 npm4MIT
- AlicenseNot gradedqualityBmaintenanceJira Cloud MCP server providing Jira-first tools for common workflows and full REST API coverage through a generic request tool.558 npmMIT
- AlicenseAqualityDmaintenanceAn 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.12625 npm13MIT
- FlicenseAqualityFmaintenanceAn MCP server that talks directly to Jira Cloud REST API v3 using static credentials and exposes tools for discovering customfield IDs, resolving account IDs, and updating issue fields including ADF JSON.13-
TDQS
Scored across 9 tools
Each tool targets a distinct action and resource: search, get, create, update, comment, transitions, transition, assign, and list projects. There is no overlap between their purposes.
All tool names consistently use the snake_case verb_noun pattern (e.g., search_issues, get_issue, create_issue). The only minor deviation is 'get_transitions' which is a noun-adjective form, but it still fits the pattern well.
9 tools is a reasonable count for a JIRA MCP server covering core operations. It covers search, CRUD, comments, transitions, assignment, and project listing without being excessive.
The tool surface covers the most common JIRA workflows: search, CRUD, commenting, status transitions, and assignment. Missing capabilities like deleting issues or managing attachments are minor gaps for a typical agent use case.