Jira MCP (Model Context Protocol) server built with FastMCP for Jira Cloud API v3
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"atlassian-jira-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Jira MCP Server A comprehensive MCP (Model Context Protocol) server for Jira Cloud integration, built with FastMCP v3. Provides 8 focused tools for complete Jira issue and project management, with automatic ADF formatting, multi-tenant HTTP support, and interactive Elicitation for guided issue creation. **Version 4.0.3** — Single-server FastMCP v3 rewrite with multi-tenant support, Elicitation, resource templates, and 321 tests. Published on [PyPI](https://pypi.org/project/atlassian-jira-mcp-server/). > **Breaking change in 4.0.0:** the CLI's console script is renamed `jira-cli` → `jira-mcp-cli`, with no alias kept. If you're upgrading from 3.4.x, update any script, alias, or MCP client config that invokes `jira-cli`. The rename matches the `jira-mcp-server` / `jira-mcp-http` family and avoids clashing with the unrelated, better-known [`jira-cli`](https://github.com/ankitpokhrel/jira-cli) project (binary `jira`), which this package's old name was easily confused with in docs and search. ## Features - **8 Focused Tools** for complete Jira issue and project management - **Interactive Elicitation** — `issue_create` and `issue_delete` interactively request missing or confirmatory input - **Streamable-HTTP + Stdio Transport** — run as an HTTP server or stdio for Claude Desktop - **Multi-Tenant HTTP** — different clients can connect with different Jira credentials per request - **Smart Field Normalization** — case-insensitive types/priorities, display-name assignee resolution, component name-to-ID lookup - **Automatic ADF Formatting** — plain text and Markdown auto-converted to Atlassian Document Format - **Transition Resolution** — use transition names ("In Progress") instead of numeric IDs - **JQL Search** with verbosity control (`ids` / `summary` / `full`), token-based pagination, and an optional approximate match count - **Jira Cloud API v3** compatibility - **Docker Support** with hot-reload development mode, loopback-bound by default - **Generated CLI** (`ji…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.