Compared · jira
18 Jira MCP servers. Which one to use.
Every Jira server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 18 servers, mostly mirrored from the MCP registry as of 2026-10-23. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Jira Alerts (JSM Operations) | io.github.rrvrs | no flag | REVIEW | 99 | npm jira-alerts-mcp |
| Jira Service Management MCP | io.github.Servosity | no flag | REVIEW | 90 | not published |
| Jira Cloud | io.github.aaronsb | no flag | REVIEW | 90 | npm @aaronsb/jira-cloud-mcp |
| jira-mini-mcp | io.github.proprock | no flag | REVIEW | 90 | pypi jira-mini-mcp |
| io.github.IamSAL/jira-easy-mcp | io.github.IamSAL | no flag | REVIEW | 85 | npm jira-easy-mcp |
| io.github.freema/mcp-jira-stdio | io.github.freema | no flag | REVIEW | 85 | npm mcp-jira-stdio |
| Jira | io.github.pipeworx-io | no flag | REVIEW | 85 | remote endpoint |
| Jira Key Shape | io.github.sadri-dridi | no flag | REVIEW | 84 | remote endpoint |
| io.github.MrRefactoring/atlassian-dc-mcp-jira | io.github.MrRefactoring | no flag | REVIEW | 80 | npm jira-datacenter-mcp |
| io.github.b1ff/atlassian-dc-mcp-jira | io.github.b1ff | no flag | REVIEW | 80 | npm @atlassian-dc-mcp/jira |
| io.github.friendlygeorge/jira-mcp-server | io.github.friendlygeorge | no flag | REVIEW | 77 | npm @supernova123/jira-mcp-server |
| com.mcparmory/atlassian-jira | com.mcparmory | no flag | REVIEW | 75 | pypi mcparmory-atlassian-jira |
| io.github.its-qusai-nasr/jira-admin-mcp | io.github.its-qusai-nasr | no flag | REVIEW | 73 | pypi jira-admin-mcp |
| io.github.raalarcon9705/jira-mcp | io.github.raalarcon9705 | no flag | REVIEW | 73 | npm raalarcon-jira-mcp-server |
| io.github.deepwired/mcp-jira-scoped | io.github.deepwired | no flag | REVIEW | 72 | npm mcp-jira-scoped |
| io.github.xcollantes/jira-mcp | io.github.xcollantes | no flag | REVIEW | 62 | pypi jira-tools-mcp |
| ai.waystation/jira | ai.waystation | no flag | REVIEW | 55 | remote endpoint |
| io.github.edrich13/mcp-jira-server | io.github.edrich13 | no flag | REVIEW | 50 | npm mcp-jira-server |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.