jira-mini-mcp
Minimal Jira Cloud MCP server: broad reads, a narrow 3-tool write surface, optional read-only mode.
The current version, v0.9.3, was published to the official MCP registry on 2026-09-18. It is distributed as jira-mini-mcp on PyPI, filed under Productivity & Project Mgmt by this index, and declares 4 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using jira-mini-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireVerdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.
Own this server? Screen its description →
That verdict was true at screening time (snapshot 2026-09-18).
Contracts can change after screening, with no version bump. The gate pins jira-mini-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
JIRA_BASE_URLYour Jira Cloud site, e.g. https://example.atlassian.net
JIRA_EMAILThe email your Jira API token belongs to
JIRA_API_TOKENA Jira Cloud API token
READ_ONLY_MODESet to true, 1, or on to register only the six read tools and withhold the three write tools
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
Submit podcast orders, check status, and manage webhooks via Barevalue editing API.