Minimal MCP server for managing Jira Cloud tickets
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-ticket-mcp","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-ticket-mcp Minimal MCP server for managing Jira Cloud tickets. The official Jira MCP server exposes a tool surface large enough to crowd out an LLM's context. This one exposes a deliberately small, curated set of tools covering the actions that actually get used. ## Configuration The server reads three settings, from environment variables or from the equivalent CLI arguments (CLI wins): | Environment variable | CLI argument | Description | |----------------------|--------------|-------------| | `JIRA_BASE_URL` | `--jira-base-url` | Your Jira site, e.g. `https://example.atlassian.net` or `https://jira.example.com` | | `JIRA_EMAIL` | `--jira-email` | The account email the API token belongs to (Cloud only) | | `JIRA_API_TOKEN` | `--jira-api-token` | A Cloud API token, or a Data Center/Server personal access token | | `JIRA_API_VERSION` | `--jira-api-version` | Force REST API `2` or `3`; autodetected from the host if unset | ## Running ```bash uvx jira-ticket-mcp --jira-base-url https://example.atlassian.net \ --jira-email you@example.com \ --jira-api-token "$JIRA_API_TOKEN" ``` As an MCP server entry, e.g. for Claude Code: ```json { "mcpServers": { "jira": { "command": "uvx", "args": ["jira-ticket-mcp"], "env": { "JIRA_BASE_URL": "https://example.atlassian.net", "JIRA_EMAIL": "you@example.com", "JIRA_API_TOKEN": "..." } } } } ``` ## Tools | Tool | What it does | |------|--------------| | `whoami` | Return the authenticated account, including its `accountId` | | `search_issues` | Search by JQL, returning a trimmed projection rather than full issues | | `get_issue` | Fetch one issue in full detail | | `list_transitions` | List the status transitions currently valid for an issue | | `create_issue` | Create an issue; `parent_key` makes it a subtask or attaches it to an epic | | `batch_create_issues` | Create many issues, returning a per-item result | | `ed…
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.