Production-ready Jira MCP Server with dual transports (stdio + HTTP/SSE) and dual auth modes (Cloud Basic + Data Center PAT)
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-server-hopcos","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 Production-ready **Jira MCP server** exposing Jira projects, issues, sprints, users, attachments, and worklogs as [Model Context Protocol](https://modelcontextprotocol.io) tools, resources, and prompts — to any MCP client (Claude Desktop, Claude Code, Cursor, VS Code) over **stdio** (local) or **HTTP/SSE / Streamable HTTP** (remote or team-shared). ``` ┌──────────────────────────────────────────────────────────────────┐ │ MCP Client │ │ Claude Desktop / Claude Code / Cursor / VS Code / custom │ └───────────────┬───────────────────────────────────┬──────────────┘ │ stdio (JSON-RPC over stdin/stdout) │ HTTP (SSE/Streamable) ▼ ▼ ┌──────────────────┐ ┌──────────────────────┐ │ stdio transport │ │ HTTP transport │ │ (default) │ │ /sse /mcp /health │ └───────┬──────────┘ └──────────┬───────────┘ │ same registered server │ ▼ ▼ ┌──────────────────────────────────────────────────────────┐ │ jira_mcp_server.server.create_server() │ │ 27 tools · 4 resources · 4 prompts (transport-agnostic) │ └───────────────────────────────┬──────────────────────────┘ ▼ ┌────────────────────────────────┐ │ JiraClient (httpx async) │ │ auth · rate-limit · retry │ └────────────────┬───────────────┘ ▼ Jira REST API / Agile API (HTTPS) ``` ## Features - **Dual transports** — stdio for local integration; HTTP with **SSE** and **Streamable HTTP** for remote/team deploy…
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.