mcp-atlassian-extended
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_PAT | No | Personal access token for Jira Data Center / self-hosted | |
| JIRA_URL | No | Jira instance URL (e.g., https://your-company.atlassian.net) | |
| JIRA_TOKEN | No | Fallback token (checked after JIRA_PERSONAL_TOKEN) | |
| JIRA_TIMEOUT | No | HTTP request timeout for Jira in seconds | 30 |
| JIRA_USERNAME | No | Email address for Jira Cloud basic auth | |
| CONFLUENCE_PAT | No | Personal access token for Confluence Data Center / self-hosted | |
| CONFLUENCE_URL | No | Confluence URL (e.g., https://your-company.atlassian.net/wiki) | |
| JIRA_API_TOKEN | No | API token for Jira Cloud basic auth | |
| JIRA_SSL_VERIFY | No | Set to 'false' to skip SSL verification for Jira | true |
| CONFLUENCE_TOKEN | No | Fallback token (checked after CONFLUENCE_PERSONAL_TOKEN) | |
| CONFLUENCE_TIMEOUT | No | HTTP request timeout for Confluence in seconds | 30 |
| ATLASSIAN_READ_ONLY | No | Set to 'true' to globally disable write operations | false |
| CONFLUENCE_USERNAME | No | Email address for Confluence Cloud basic auth | |
| JIRA_PERSONAL_TOKEN | No | Fallback personal access token (checked after JIRA_PAT) | |
| CONFLUENCE_API_TOKEN | No | API token for Confluence Cloud basic auth | |
| CONFLUENCE_SSL_VERIFY | No | Set to 'false' to skip SSL verification for Confluence | true |
| CONFLUENCE_PERSONAL_TOKEN | No | Fallback personal access token (checked after CONFLUENCE_PAT) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_get_attachmentsC | List attachments on a Jira issue. |
| jira_upload_attachmentB | Upload a file as an attachment to a Jira issue. |
| jira_download_attachmentA | Download a Jira attachment into the download directory (default
|
| jira_delete_attachmentC | Delete a Jira attachment. |
| jira_search_usersC | Search for Jira users. |
| jira_list_projectsB | List all accessible Jira projects. |
| jira_list_fieldsC | List Jira fields, optionally filtered. |
| jira_backlogB | Get backlog issues for a board. Returns a compact field set by default (summary, status, issue type, priority,
assignee, labels). Pass |
| jira_get_project_versionsB | List all versions for a Jira project (REST API v2, supports Server/DC and Cloud). |
| jira_create_versionB | Create a new version in a Jira project (REST API v2, supports Server/DC and Cloud). |
| jira_update_versionB | Update an existing Jira version (REST API v2, supports Server/DC and Cloud). |
| jira_get_boardC | Get details of a Jira agile board. |
| jira_board_configC | Get board column/status configuration. |
| jira_get_sprintC | Get details of a specific sprint. |
| jira_move_to_sprintC | Move issues into a sprint. |
| jira_create_issueA | Create a Jira issue with standard and custom fields. Pass custom_fields example: {"customfield_10004": 5, "customfield_12345": {"value": "MyTeam"}} |
| jira_update_issueC | Update a Jira issue's standard and custom fields. |
| jira_create_linkC | Create a link between two Jira issues. |
| jira_delete_linkB | Delete a Jira issue link by its ID. |
| confluence_list_calendarsA | List Confluence calendars, optionally narrowed by type or a name/space search. |
| confluence_get_time_offA | Get time-off events for a date range across all leave calendars. Pass |
| confluence_sprint_capacityB | Calculate sprint capacity considering team time-off. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_ticket | Create a Jira ticket — gather fields, set custom fields (points, DoD, privacy, security), create issue, and add links. project_key accepts a full Jira project URL. |
| plan_sprint | Plan a sprint — review backlog, calculate capacity, suggest scope, and move issues into the sprint. Its final step moves issues into the sprint (``jira_move_to_sprint``), so it is tagged ``write`` and hidden when the server is locked read-only. board_id accepts a full Jira board URL. |
| close_ticket | Close a Jira ticket — verify DoD, check linked MRs, transition statuses, and add closing comment. issue_key accepts a full Jira browse URL (e.g. https://jira.example.com/browse/PROJ-123). |
| team_availability | Check team availability — get time-off, calculate capacity, and flag scheduling conflicts. |
| manage_attachments | Manage issue attachments — list, identify stale/duplicates, upload/download, and clean up. issue_key accepts a full Jira browse URL (e.g. https://jira.example.com/browse/PROJ-123). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Jira Issue Hierarchy | Epic → Story → Task → Subtask structure, splitting rules, and type selection |
| Jira Ticket Writing Standards | Summary format, Story/Bug/Task/Spike description templates, comment policy |
| Acceptance Criteria Standards | Given/When/Then format, rule-oriented criteria, writing rules |
| Sprint Hygiene Rules | Definition of Ready, WIP limits, carry-over policy, refinement standards |
| Jira Workflow & Automation | Status transitions, automation rule patterns, workflow governance |
| Issue Linking Best Practices | Link types, correct usage, cross-team patterns, cleanup |
| Story Point Estimation | Fibonacci scale, Planning Poker, relative sizing, velocity |
| Definition of Done Checklists | Story/Bug/Task DoD templates, enforcement rules, governance |
| Jira Label Taxonomy | Standard labels, naming rules, governance, JQL usage |
| JQL Query Library | 15 query patterns for sprint management, blockers, stale tickets, reporting |
| Jira Custom Field Governance | Creation process, naming conventions, field contexts, audit |
| Confluence Space Organization | Space taxonomy, page hierarchy, naming conventions, maintenance |
| Agile Ceremony Standards | Sprint planning, standup, review, retrospective formats and rules |
| Git-Jira Integration Patterns | Branch naming for auto-linking, smart commits, automation rules, macros |
| Confluence Page Templates | ADR, RFC, Runbook, Retrospective, DACI, and Meeting Notes templates |
TDQS
Scored across 22 tools
Most tools target clearly distinct resources: attachments (list/download/upload/delete), versions (create/update/list), boards/sprints, and Confluence calendars are well separated. Minor potential confusion exists around board-related tools (jira_get_board, jira_board_config, jira_backlog) and sprint tools, but descriptions disambiguate them adequately.
Names follow a consistent 'product_verb_noun' snake_case convention with jira_/confluence_ prefixes throughout, which is highly predictable. A few entries are noun-only (jira_board_config, jira_backlog, confluence_sprint_capacity) rather than verb-led, a minor deviation from the rest.
22 tools is on the heavier side but justified by an 'extended' server spanning two products (Jira and Confluence) with agile, attachment, version, and time-off domains. Each tool maps to a distinct operation, so little feels redundant despite the count.
Coverage is uneven: attachments have full lifecycle and versions have create/update/list, but there is no issue search/get, no delete-issue, no comment tools, and no delete-version. An agent can create and update issues but lacks a general way to retrieve or search them beyond the backlog endpoint.