Model Context Protocol server for Jira integration
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-tools","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.
# MCP Server for JIRA A Model Context Protocol (MCP) server that provides seamless integration with Jira. This server enables AI assistants to retrieve issue information, comments, and attachments from any Jira instance. ## Features - 🎫 **Issue Management**: Get, create, update, and transition issues - 🔍 **Advanced Search**: JQL-based issue search with custom fields - 📊 **Epic & Sprint Tracking**: Monitor progress, story points, and completion - 🔗 **Issue Relationships**: View and manage issue links - 💬 **Comments**: Add and retrieve issue comments - 📎 **Attachments**: Download issue attachments - 📜 **History**: Track all changes to issues - 🚀 **Release Management**: View project versions and releases - 👥 **Assignment**: Assign/unassign issues to users - 🔒 **Secure Authentication**: Uses Jira API tokens ## Prerequisites - Python 3.10 or higher - Jira API token ([How to create](https://jsw.ibm.com/plugins/servlet/de.resolution.apitokenauth/admin)) - UV package manager ([Installation guide](https://docs.astral.sh/uv/getting-started/installation/)) ## Installation ### MCP Client Configuration For Bob, go to Settings > MCP > Global MCPs. Add to your MCP client configuration: ```json { "mcpServers": { "jira": { "command": "uvx", "args": ["jira-mcp-tools"], "env": { "JIRA_URL": "https://jsw.ibm.com/", "JIRA_EMAIL": "your-email@ibm.com", "JIRA_TOKEN": "your-api-token" } } } } ``` ## Available Tools ### Issue Operations - **`get_jira_ticket_info(issue_key)`** - Get issue details, description, and comments - **`get_jira_ticket_attachments(issue_key)`** - Download issue attachments - **`get_issue_history(issue_key)`** - View complete change history - **`get_issue_links(issue_key)`** - Get linked issues (blocks, relates to, etc.) - **`get_development_links(issue_key)`** - Get GitHub branches, PRs, and commits ### Search & Query - **`search_issues(jql, max_results=50, fields=None)`** - JQL-based …
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.