jira-integrationlisted

# Jira Integration Two access paths: the `mcp-atlassian` MCP server (exposes Jira as tools) or direct REST API v3 calls with basic auth (`email:api_token`). ## MCP Server Setup Requires Python 3.10+ and `uvx` (from `uv`). Add to `mcpServers` in `~/.claude.json`: ```json { "jira": { "command": "uvx", "args": ["mcp-atlassian==0.21.0"], "env": { "JIRA_URL": "https://YOUR_ORG.atlassian.net", "JIRA_EMAIL": "your.email@example.com", "JIRA_API_TOKEN": "your-api-token" } } } ``` API tokens are created at https://id.atlassian.com/manage-profile/security/api-tokens. Prefer system environment variables over the `env` block for anything committed. ### Tools exposed by mcp-atlassian | Tool | Purpose | |------|---------| | `jira_search` | JQL queries | | `jira_get_issue` | Fetch full issue by key | | `jira_create_issue` | Create Task, Bug, Story, Epic | | `jira_update_issue` | Update summary, description, assignee, fields | | `jira_transition_issue` | Change status | | `jira_get_transitions` | List available transitions for an issue | | `jira_add_comment` | Add a comment | | `jira_get_sprint_issues` | List issues in a sprint | | `jira_create_issue_link` | Link issues (Blocks, Relates to) | | `jira_get_issue_development_info` | Linked PRs, branches, commits | Transition IDs vary per project workflow, so call `jira_get_transitions` before `jira_transition_issue`. ## REST API v3 Environment: `JIRA_URL` (e.g. `https://yourorg.atlassian.net`), `JI