Native async Jira Cloud MCP server
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":"jira-mcp-atlassian","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 Cloud MCP Native async Python MCP server for Jira Cloud REST API v3 and Jira Server/Data Center REST API v2. Cloud uses `JIRA_EMAIL` + `JIRA_TOKEN`; Data Center uses `JIRA_PERSONAL_TOKEN` or `JIRA_USERNAME` + `JIRA_PASSWORD`. Configure the matching variables and run: ```bash uv sync uv run jira-mcp ``` The URL determines the API mode automatically: `*.atlassian.net` uses Cloud endpoints, while other hosts use Data Center endpoints. Exposes JQL search, issue CRUD, comments, transitions, assignment, project, and issue-type tools. Jira descriptions and comments use ADF in Cloud and wiki markup strings in Data Center. Build with `uv build`; publish with `UV_PUBLISH_TOKEN=pypi-... uv publish`. The package name is `jira-mcp-atlassian`.
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.