An MCP server for interacting with Jira using username/password authentication.
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-2","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 (using FastMCP) This MCP server provides tools for interacting with a Jira instance using username/password or session cookie authentication via the FastMCP framework. It allows LLMs (like Claude) to query, update, and manage Jira issues. ## Features * Connects to Jira using Basic Auth (username/password) or Session Cookie. * Provides MCP tools for common Jira operations: * Fetching single or multiple issues. * Creating and updating issues. * Transitioning issue statuses. * Listing available transitions. * Adding comments. * Downloading attachments. * Listing project issue types. * Built with the modern and efficient FastMCP framework. ## Prerequisites * Python 3.10+ * [uv](https://github.com/astral-sh/uv) (Recommended Python package installer and virtual environment manager) * Access to a Jira instance (Cloud or Server/Data Center). ## Setup 1. **Clone the Repository:** ```bash git clone <your-repo-url> cd jira-mcp-server ``` 2. **Configure Environment Variables:** * Copy the example environment file: ```bash cp .env.example .env ``` * **Edit the `.env` file** with your Jira instance details: * `JIRA_BASE_URL`: The full URL of your Jira instance (e.g., `https://yourcompany.atlassian.net` or `https://jira.yourdomain.com`). * **Choose ONE authentication method:** * **Method 1: Username/Password:** Set `JIRA_USERNAME` and `JIRA_PASSWORD`. (Note: For Jira Cloud, you might need an API Token instead of your password). * **Method 2: Session Cookie:** Set `JIRA_SESSION_ID`. Get this value by logging into Jira in your browser, opening developer tools, going to Application/Storage -> Cookies, finding the cookie named `JSESSIONID` for your Jira domain, and copying its value. Session ID authentication takes precedence if set. * **Important:** The `.env` file contains sensitive credentials an…
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.