A
licenseB
qualityB
maintenanceAn open-source Model Context Protocol (MCP) server for Atlassian Jira and Confluence Cloud, enabling LLMs to search, read, write, and manage issues and pages.
22
2
MIT
raalarcon-jira-mcp-server
Related Servers
Alternatives to raalarcon-jira-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for Jira Cloud — gives AI agents full context and control over Jira issues, projects, sprints, and workflows.44 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects your AI IDE to Jira. Query your tickets, active sprint, and issue details directly from GitHub Copilot, Cursor, Claude Desktop, or any MCP-compatible client.16 npmISC
- AlicenseBqualityCmaintenanceLightweight MCP server for Jira, Confluence, and Bitbucket — read, create, and update from your AI IDE.20MIT
- 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
- AlicenseNot gradedqualityCmaintenanceA lightweight MCP server that exposes Jira issue operations (get, search, create) as tools for AI clients like Claude.43 npmISC
TDQS
A3.7/5.0
Scored across 24 tools
Disambiguation5/5
Each tool targets a distinct action and resource (issues, sprints, comments, boards, users, wiki). There is no overlap; for example, get_issue and get_sprint_issues serve different purposes, and move_issue_to_sprint is clearly different from get_sprint_issues.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with underscores (e.g., assign_issue, close_sprint, create_comment). Even query_wiki fits this pattern. No mixing of styles or vague verbs.
Tool Count4/5
24 tools is reasonable for a Jira server covering issues, sprints, comments, boards, users, and wiki. It is slightly on the higher side but well-scoped for the complexity of Jira operations.
Completeness4/5
The surface covers core CRUD for issues, comments, and sprints, plus transitions, agile boards, and user search. Minor gaps like issue linking or attachments are absent, but the essential workflows for an agent are well covered.
Maintenance
ActivityInactive
ResponsivenessUnresponsive