jira-aie-mcp

# jira-aie-mcp An MCP server for the AIE team's Jira instance. Exposes the two things `mcp-atlassian` can't do natively: 1. **Rich Atlassian Document Format (ADF) issue creation/update** — info / warning / success / error / note **panels**, inline **status lozenges**, **date chips**, **expand/collapse** blocks, and **task lists**. Accepts a Markdown string, a compact block-list DSL, or a pre-built ADF doc. 2. **Working-day gantt scheduler** — reads Blocks dependencies and Original Estimates from a JQL-scoped set of issues, computes start/end dates on the Norwegian public-holiday calendar, and optionally writes the end dates back to each issue's `duedate` field. Plus a **semantic link shortcut** (`jira_link_issues`) that picks the right inward/outward direction for Blocks, Relates, Duplicates, Clones, and Causes without forcing the caller to memorise Jira's link model. `mcp-atlassian` still handles everything else — search, transitions, comments, watchers, worklogs, etc. This server is a **gap-filler**, not a replacement. ## Install Run it on demand with `uvx` — no install step needed; `uvx` fetches the package from PyPI into an ephemeral environment on first use and caches it for subsequent runs: ```bash uvx jira-aie-mcp ``` Or install it as a persistent tool: ```bash uv tool install jira-aie-mcp jira-aie-mcp ``` Either form starts the server on stdio, which is what MCP clients expect. ## Configure (MCP client) All configuration lives in the MCP client's server definition — no separate config file. Minimum required env vars: | Variable | Required | Default | | --- | --- | --- | | `JIRA_BASE_URL` | yes | — | | `JIRA_EMAIL` | yes | — | | `JIRA_API_TOKEN` | yes | — | | `JIRA_DEFAULT_PROJECT_KEY` | no | — (fallback for `jira_create_issue` when the tool call omits `project_key`) | | `JIRA_WORKSTREAM_FIELD_ID` | no | — (tenant-specific custom field ID, e.g. `customfield_10742`, that `schedule_compute` groups by in the Mermaid gantt) | Gene…