Jira & Confluence MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLASSIAN_URL | Yes | Your Atlassian base URL, e.g. https://yourco.atlassian.net | |
| ATLASSIAN_EMAIL | Yes | Your Atlassian account email | |
| ATLASSIAN_API_TOKEN | Yes | API token from id.atlassian.com |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_list_projectsA | List all accessible Jira projects. |
| jira_get_projectA | Get details of a specific Jira project by its key. |
| jira_get_issueA | Get full details of a Jira issue including its status, assignee, description, comments, and available transitions. |
| jira_search_issuesA | Search Jira issues using JQL (Jira Query Language). JQL must include at least one filter condition. Examples: 'project=PROJ AND status=Open', 'assignee=currentUser() ORDER BY created DESC', 'project=PROJ AND sprint in openSprints()'. Pagination uses nextPageToken from previous response. |
| jira_create_issueA | Create a new Jira issue. Provide project_key, summary, and issue_type at minimum. issue_type is usually 'Story', 'Bug', 'Task', or 'Epic'. |
| jira_update_issueA | Update fields of an existing Jira issue. Only provide the fields you want to change. |
| jira_delete_issueB | Delete a Jira issue permanently. |
| jira_get_transitionsA | Get all available workflow transitions for a Jira issue (e.g., 'In Progress', 'Done'). |
| jira_transition_issueA | Move a Jira issue to a new status using a workflow transition. |
| jira_get_commentsA | Get all comments on a Jira issue. |
| jira_add_commentB | Add a comment to a Jira issue. |
| jira_update_commentB | Update an existing comment on a Jira issue. |
| jira_delete_commentB | Delete a comment from a Jira issue. |
| jira_assign_issueA | Assign or unassign a Jira issue. Pass null for account_id to unassign. |
| jira_search_usersB | Search Jira users by name or email. |
| jira_get_current_userA | Get the currently authenticated Jira user. |
| jira_list_boardsB | List Jira Agile boards, optionally filtered by project. |
| jira_get_boardB | Get details of a specific Jira board. |
| jira_get_board_issuesC | Get issues on a Jira board, optionally filtered by JQL. |
| jira_get_board_backlogC | Get issues in a board's backlog. |
| jira_list_sprintsA | List sprints for a board. Filter by state: active, future, closed. |
| jira_get_sprintB | Get details of a specific sprint. |
| jira_create_sprintB | Create a new sprint on a board. |
| jira_update_sprintA | Update a sprint (name, goal, dates, or state). Use state='active' to start, state='closed' to complete. |
| jira_get_sprint_issuesC | Get all issues in a sprint. |
| jira_move_issues_to_sprintC | Move one or more issues into a sprint. |
| jira_move_issues_to_backlogA | Move one or more issues back to the backlog (remove from sprint). |
| jira_get_issue_typesA | Get available issue types, optionally for a specific project. |
| jira_get_prioritiesA | Get all available issue priorities. |
| jira_get_fieldsA | Get all Jira fields including custom fields. |
| jira_get_labelsC | Get available labels in Jira. |
| jira_add_worklogB | Log work time against a Jira issue. |
| jira_get_worklogsB | Get all worklogs for a Jira issue. |
| jira_get_watchersB | Get watchers of a Jira issue. |
| jira_add_watcherB | Add a user as a watcher to a Jira issue. |
| jira_get_link_typesA | Get all available issue link types (e.g. 'blocks', 'is blocked by', 'clones'). |
| jira_link_issuesC | Create a link between two Jira issues. |
| confluence_list_spacesA | List all Confluence spaces accessible to the authenticated user. |
| confluence_get_spaceA | Get details of a Confluence space by its ID. |
| confluence_get_space_by_keyB | Get a Confluence space by its key (e.g. 'TEAM', 'DEV'). |
| confluence_get_pageB | Get a Confluence page by its ID, including its body content. |
| confluence_list_pages_in_spaceB | List pages in a Confluence space, optionally filtered by title. |
| confluence_get_child_pagesC | Get child pages of a Confluence page. |
| confluence_create_pageA | Create a new Confluence page. body_value should be Confluence Storage Format (XHTML-like). Example: 'Hello World' |
| confluence_update_pageA | Update an existing Confluence page. You MUST provide the current version_number (get from confluence_get_page). The version number must be incremented by 1. |
| confluence_delete_pageB | Delete a Confluence page by ID. |
| confluence_get_page_labelsC | Get labels on a Confluence page. |
| confluence_add_page_labelsB | Add labels to a Confluence page. |
| confluence_delete_page_labelB | Remove a label from a Confluence page. |
| confluence_searchB | Search Confluence content (pages, blog posts, etc.) by text query. |
| confluence_get_page_ancestorsB | Get the ancestor pages (breadcrumb path) of a Confluence page. |
| confluence_get_page_commentsC | Get footer comments on a Confluence page. |
| confluence_add_page_commentC | Add a footer comment to a Confluence page. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 53 tools
Each tool is clearly prefixed with 'confluence_' or 'jira_', and within each domain, they target distinct actions and resources (e.g., create vs. get, page vs. space vs. issue, comments vs. labels). There is no ambiguity between tools.
All tools follow a consistent pattern: product prefix + verb_noun (e.g., jira_create_issue, confluence_get_page). The naming conventions are uniform and predictable across the entire set.
With 53 tools covering two major platforms, the count is high but justifiable. Each tool serves a specific purpose, and the scope is broad. However, some consolidation (e.g., a single get_issues with optional filters) could reduce redundancy without losing functionality.
The tool set covers most CRUD operations, search, comments, labels, sprints, boards, and workflows for both Jira and Confluence. Notable omissions include file attachments (e.g., adding attachments to issues or pages) and creating Confluence blog posts, but core workflows are well-supported.