Jira & Confluence MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERBOSE | No | Enable debug logging (set to 'true') | |
| JIRA_URL | No | Override Jira URL (overrides ATLASSIAN_URL for Jira) | |
| MCP_PORT | No | Port for the MCP server (default: 9339) | 9339 |
| ATLASSIAN_URL | Yes | Your Atlassian instance URL (e.g., https://your-org.atlassian.net) | |
| CONFLUENCE_URL | No | Override Confluence URL (overrides ATLASSIAN_URL for Confluence) | |
| JIRA_API_TOKEN | No | Override Jira API token (overrides ATLASSIAN_API_TOKEN for Jira) | |
| ATLASSIAN_EMAIL | Yes | Your email address for Atlassian API authentication | |
| JIRA_PROJECT_KEY | No | Restrict Jira operations to a specific project key | |
| IGNORE_TLS_ERRORS | No | Set to 'true' to ignore TLS errors (useful in corporate networks) | false |
| ATLASSIAN_API_TOKEN | Yes | Your Atlassian API token (get from https://id.atlassian.com/manage-profile/security/api-tokens) | |
| CONFLUENCE_API_TOKEN | No | Override Confluence API token (overrides ATLASSIAN_API_TOKEN for Confluence) | |
| CONFLUENCE_SPACE_KEY | No | Restrict Confluence operations to a specific space key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_confluenceC | Search Confluence pages using a CQL (Confluence Query Language) query string. |
| get_confluence_pageB | Read a Confluence page by its ID. Returns the page title, space, version, URL, and full body content in Confluence storage format (HTML). |
| create_confluence_pageA | Create a new Confluence page in a given space. REQUIRED: Always provide Markdown content. Supports headers, lists, bold, italic, code blocks, tables, links, images, and more. Content is automatically converted to Confluence storage format (HTML). Optionally nest the page under a parent page. |
| update_confluence_pageB | Update an existing Confluence page. REQUIRED: Always provide Markdown content. Supports headers, lists, bold, italic, code blocks, tables, links, images, and more. Content is automatically converted to Confluence storage format (HTML). Automatically handles version bumping. |
| add_confluence_commentB | Add an inline comment to an existing Confluence page. REQUIRED: Always provide Markdown content. Supports bold, italic, links, and basic formatting. Content is automatically converted to Confluence storage format (HTML). |
| get_confluence_page_versionsB | Get the version history of a Confluence page. Returns a list of versions with author, timestamp, and optional version message. |
| check_confluence_permissionsA | Check whether the configured API token is valid and has the required permissions. Validates authentication, read/search access, and optionally write access to a specific page. |
| jira_searchB | Search Jira issues using a JQL (Jira Query Language) query string. Returns a list of matching issues with key details including status, assignee, priority, and description. |
| jira_get_issueA | Get full details of a single Jira issue by its key (e.g. 'PROJ-123') or numeric ID. Returns summary, status, type, priority, assignee, reporter, description, labels, and timestamps. |
| jira_create_issueA | Create a new Jira issue (Story, Bug, Task, etc.) in a given project. New issues are created unassigned by default. REQUIRED: Always provide a markdown-formatted description. |
| jira_update_issueA | Update one or more fields on an existing Jira issue. Provide only the fields you want to change. When updating description, ALWAYS use Markdown format. Supports summary, description (Markdown format), assignee (accountId), priority, labels, and any other valid Jira field. |
| jira_transition_issueA | Change the status of a Jira issue by performing a workflow transition. Accepts either a transition name (e.g. 'In Progress', 'Done') or a numeric transition ID. Use jira_get_issue to see the current status first. |
| jira_get_transitionsA | List all available workflow transitions for a Jira issue. Use this to discover valid transition names before calling jira_transition_issue. |
| jira_add_commentB | Add a new comment to a Jira issue (Story, Bug, Task, etc.) by its key or numeric ID. REQUIRED: Always provide a Markdown-formatted comment body. Use headers (# ## ###), lists (*, -), bold (text), italic (text), code ( |
| jira_update_commentA | Update the body of an existing comment on a Jira issue. Identify the comment by the issue key/ID and the comment ID (returned by jira_add_comment). REQUIRED: Always provide the new Markdown-formatted comment body. Automatically converted to Atlassian Document Format (ADF) for Jira Cloud. Note: comments cannot be deleted through this server. |
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 15 tools
Every tool has a clearly distinct resource+action target, and the Confluence/Jira split is reinforced by consistent naming. The only mild adjacency is jira_update_issue vs jira_transition_issue, but the descriptions make the workflow-transition distinction explicit.
Jira tools use a uniform 'jira_verb_noun' prefix pattern, but Confluence tools use a suffix form (search_confluence, get_confluence_page, add_confluence_comment), so the two families follow different conventions. Each family is internally readable, but the set as a whole mixes styles.
15 tools split cleanly across two products (8 Jira, 7 Confluence) is well-scoped for a combined server. Each tool covers a distinct operation with no filler.
Core lifecycle is covered for both domains: search/get/create/update plus comments and transitions for Jira, and search/get/create/update/comments/versions/permissions for Confluence. Gaps remain around deletes (no Jira or Confluence delete, and comments explicitly cannot be deleted) and Jira attachment/sprint operations, but these are workable omissions.