jira-mini-mcp
Minimal Jira Cloud MCP server: broad reads, a narrow 3-tool write surface, optional read-only mode.
The current version, v1.3.0, was published to the official MCP registry on 2026-09-19. It is distributed as jira-mini-mcp on PyPI, filed under Productivity & Project Mgmt by this index, and declares 9 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-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“No malicious instructions”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-11-02).
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
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for jira-mini-mcp](https://mcpindex.ai/server/io-github-proprock-jira-mini-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-proprock-jira-mini-mcp">Independent trust record for jira-mini-mcp</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-proprock-jira-mini-mcp)<a href="https://mcpindex.ai/server/io-github-proprock-jira-mini-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-proprock-jira-mini-mcp" alt="mcpindex verdict" height="20" /></a>JIRA_BASE_URLYour Jira Cloud site, e.g. https://example.atlassian.net
JIRA_AUTH_METHODapi_token (default) or oauth; oauth needs an OAuth 2.0 (3LO) app and a one-time `jira-mini-mcp login`
JIRA_EMAILThe email your Jira API token belongs to (JIRA_AUTH_METHOD=api_token)
JIRA_API_TOKENA Jira Cloud API token (JIRA_AUTH_METHOD=api_token)
JIRA_OAUTH_CLIENT_IDClient ID of your OAuth 2.0 (3LO) app (JIRA_AUTH_METHOD=oauth)
JIRA_OAUTH_CLIENT_SECRETSecret of your OAuth 2.0 (3LO) app (JIRA_AUTH_METHOD=oauth)
READ_ONLY_MODESet to true, 1, or on to register only the six read tools and withhold the three write tools
STRUCTURED_OUTPUTSet to true, 1, or on to also send structuredContent and an outputSchema; by default each result is sent once, in content
DISABLE_STRUCTURED_OUTPUTWith STRUCTURED_OUTPUT=true, comma-separated tool names that still return content only, without structuredContent
Ask what your team decided in meetings, get your standup, and update Jira/Linear-synced tasks.
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders
Jira & Confluence MCP: 24 tools for issues, sprints, comments, transitions & wiki. Run via npx.