Skip to main content
Glama

Atlassian MCP Server

An MCP server for Jira and Confluence Cloud. Write in markdown — the server converts to Atlassian Document Format (ADF) automatically.

Quickstart

git clone https://github.com/tingyiy/atlassian-mcp-server.git
cd atlassian-mcp-server
pip install -r requirements.txt   # or: uv pip install -r requirements.txt

Then add it to your MCP client (see Configuration below).

You'll need an Atlassian API token and these values:

Variable

Example

ATLASSIAN_USERNAME

you@company.com

ATLASSIAN_API_KEY

your API token

JIRA_URL

https://your-domain.atlassian.net/rest/api/3

CONFLUENCE_URL

https://your-domain.atlassian.net/wiki

CONFLUENCE_SPACE_KEY

ENG (optional, default space)

Related MCP server: Jira

Tools

Jira

Tool

Description

list_jira_issues

Search issues using JQL

read_jira_issue

Get full issue details

jira_create_issue

Create an issue (markdown description)

jira_update_issue

Update summary or description (markdown)

jira_add_comment

Add a comment (markdown)

jira_get_comments

Retrieve all comments

jira_get_attachment_image

Download an attachment by ID

jira_transition_issue

Move issue through workflow

jira_get_transitions

List available transitions

Confluence

Tool

Description

list_confluence_pages

List pages in a space

view_confluence_page

Get page content and metadata

confluence_create_page

Create a page (optionally nested)

edit_confluence_page

Update a page (auto-increments version)

confluence_delete_page

Delete a page

confluence_search

Search using CQL

confluence_get_comments

Get all comments on a page

confluence_add_comment

Add a comment (with reply support)

confluence_get_attachment_image

Download an image attachment

Markdown Support

Jira tools (jira_create_issue, jira_update_issue, jira_add_comment) accept markdown for descriptions and comments. The server converts it to ADF behind the scenes using md2adf.

Supported formatting: headings, bold, italic, strikethrough, inline code, links, images, code blocks (with language), bullet/ordered/nested lists, blockquotes, horizontal rules, and tables.

Configuration

Claude Code

Add to ~/.claude.json:

{
  "mcpServers": {
    "atlassian": {
      "type": "stdio",
      "command": "python3",
      "args": ["/path/to/atlassian-mcp-server/server.py"],
      "env": {
        "ATLASSIAN_USERNAME": "you@company.com",
        "ATLASSIAN_API_KEY": "your_api_token",
        "JIRA_URL": "https://your-domain.atlassian.net/rest/api/3",
        "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
        "CONFLUENCE_SPACE_KEY": "ENG"
      }
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "atlassian": {
      "command": "python3",
      "args": ["/path/to/atlassian-mcp-server/server.py"],
      "env": {
        "ATLASSIAN_USERNAME": "you@company.com",
        "ATLASSIAN_API_KEY": "your_api_token",
        "JIRA_URL": "https://your-domain.atlassian.net/rest/api/3",
        "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
        "CONFLUENCE_SPACE_KEY": "ENG"
      }
    }
  }
}

Cursor / VS Code

Add to .cursor/mcp.json or .vscode/mcp.json:

{
  "mcpServers": {
    "atlassian": {
      "command": "python3",
      "args": ["/path/to/atlassian-mcp-server/server.py"],
      "env": {
        "ATLASSIAN_USERNAME": "you@company.com",
        "ATLASSIAN_API_KEY": "your_api_token",
        "JIRA_URL": "https://your-domain.atlassian.net/rest/api/3",
        "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki"
      }
    }
  }
}

Make sure the python3 in command points to an environment with the dependencies installed. To be explicit, use the full path (e.g. /path/to/venv/bin/python).

Notes

Mermaid Diagrams in Confluence

Confluence's Mermaid plugin stores diagram source internally, so the MCP tools can't render them programmatically. Instead, provide the Mermaid source in a code block — the user can then convert it in the Confluence editor.

License

MIT — see LICENSE.

Available Tools

22 tools
confluence_add_commentB

Adds a comment to a Confluence page. Set parent_comment_id to reply to an existing comment.

Inputs: page_id (required), body (required), parent_comment_id. Returns: result

confluence_create_pageC

Creates a new Confluence page, optionally under a parent page.

Inputs: title (required), content (required), parent_id, space_key. Returns: result

confluence_delete_pageC

Deletes a Confluence page.

Inputs: page_id (required). Returns: result

confluence_get_attachment_imageC

Gets an image attachment on a Confluence page and returns it as an Image.

Inputs: page_id (required), filename (required).

confluence_get_commentsC

Gets all comments for a Confluence page.

Inputs: page_id (required). Returns: result

edit_confluence_pageB

Updates a Confluence page. If version is not provided, it will be automatically incremented.

MERMAID DIAGRAMS: Confluence Cloud uses the Mermaid Diagrams plugin. You CANNOT create rendered diagrams programmatically. The mermaid-cloud macro only references diagram content in the plugin's internal storage (not accessible via API).

To include a Mermaid diagram, provide it as a code block for the user to manually convert: <ac:structured-macro ac:name="code" ac:schema-version="1"> <ac:parameter ac:name="language">text</ac:parameter> ac:plain-text-body</ac:plain-text-body> </ac:structured-macro>

The user can then convert this code block to a rendered diagram in the Confluence editor.

Inputs: page_id (required), title (required), content (required), version. Returns: result

jira_add_commentA

Adds a comment to a Jira issue.

Args: issue_key: The ID or key of the issue. comment: The comment content in markdown. Supports headings, bold, italic, strikethrough, links, code blocks, lists, tables, etc.

Mentioning users: To tag a user, first call jira_search_users to find their accountId, then use @[accountId] in the text (e.g. @[712020:abc123]). You can also use @username which auto-resolves if there is exactly one match, but will fail if ambiguous — prefer @[accountId].

Inputs: issue_key (required), comment (required). Returns: result

jira_create_issueA

Creates a new Jira issue. For description, accepts a markdown string. Supports headings, bold, italic, strikethrough, links, code blocks, lists, tables, etc.

Mentioning users: To tag a user, first call jira_search_users to find their accountId, then use @[accountId] in the text (e.g. @[712020:abc123]). You can also use @username which auto-resolves if there is exactly one match, but will fail if ambiguous — prefer @[accountId].

Inputs: project_key (required), summary (required), description, issuetype. Returns: result

jira_delete_commentA

Deletes a comment from a Jira issue.

Args: issue_key: The ID or key of the issue. comment_id: The ID of the comment to delete (from jira_get_comments).

Inputs: issue_key (required), comment_id (required). Returns: result

jira_download_attachmentB

Downloads a Jira attachment by ID, saves it to a temp file, and returns the file path.

Inputs: attachment_id (required). Returns: result

jira_edit_commentA

Edits an existing comment on a Jira issue.

Args: issue_key: The ID or key of the issue. comment_id: The ID of the comment to edit (from jira_get_comments). comment: The new comment content in markdown. Supports headings, bold, italic, strikethrough, links, code blocks, lists, tables, etc.

Mentioning users: To tag a user, first call jira_search_users to find their accountId, then use @[accountId] in the text (e.g. @[712020:abc123]). You can also use @username which auto-resolves if there is exactly one match, but will fail if ambiguous -- prefer @[accountId].

Inputs: issue_key (required), comment_id (required), comment (required). Returns: result

jira_get_commentsB

Gets all comments for a Jira issue.

Inputs: issue_key (required). Returns: result

jira_get_transitionsC

Gets available transitions for a Jira issue.

Inputs: issue_key (required). Returns: result

jira_list_fieldsA

Lists all available Jira fields (standard and custom).

Use this to discover field IDs you can pass as additional_fields to read_jira_issue, list_jira_issues, or jira_update_issue.

Inputs: no named parameters. Returns: result

jira_search_usersA

Searches for Jira users by name or email.

Args: query: Name, email, or username fragment to search for. max_results: Maximum number of results to return.

Inputs: query (required), max_results. Returns: result

jira_transition_issueA

Transitions a Jira issue to a new status using a transition ID. Use jira_get_transitions to find available transition IDs.

Inputs: issue_key (required), transition_id (required). Returns: result

jira_update_issueA

Updates fields on a Jira issue.

Args:
    issue_key: The issue key (e.g. "PROJ-123").
    summary: New summary text.
    description: New description in markdown. Supports headings, bold,
        italic, strikethrough, links, code blocks, lists, tables, etc.
    additional_fields: Dict of field_id -> value for simple fields
        (plain text, dates, numbers, selects).
        Use jira_list_fields to discover field IDs.
        Example: {"duedate": "2026-04-01", "labels": ["bug"]}
    rich_text_fields: Dict of field_id -> markdown string for rich text
        fields that need ADF conversion (e.g. Developer Notes,
        Deployment Info). These get converted to Atlassian Document
        Format automatically.
        Example: {"customfield_10402": "## Plan
  • Step 1

  • Step 2"}

    Mentioning users (in description and rich_text_fields): First call jira_search_users to find the accountId, then use @[accountId] in the text (e.g. @[712020:abc123]).

Inputs: issue_key (required), summary, description, additional_fields, +1 more. Returns: result

list_confluence_pagesC

Lists Confluence pages in a space.

Inputs: space_key, limit. Returns: result

list_jira_issuesA

Lists Jira issues using JQL.

By default returns key, summary, status, priority, assignee. Use additional_fields to include extra Jira fields in the response.

Args: jql: JQL query string. next_page_token: Token for pagination (returned in previous response). max_results: Maximum number of results to return. additional_fields: Extra Jira field names to include, e.g. ["issuetype", "labels", "created", "updated", "duedate", "components", "fixVersions", "reporter", "resolution", "parent", "subtasks"].

Inputs: jql, next_page_token, max_results, additional_fields. Returns: result

read_jira_issueA

Gets details of a specific Jira issue.

By default returns a compact set of fields. Use additional_fields to request more without bloating every response.

Args: issue_key: The issue key (e.g. "PROJ-123"). additional_fields: Extra Jira field names to include, e.g. ["components", "fixVersions", "duedate", "resolution", "parent", "subtasks", "issuetype", "customfield_XXXXX"].

Inputs: issue_key (required), additional_fields. Returns: result

view_confluence_pageC

Gets the content of a Confluence page.

Inputs: page_id (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 22 tools

    Disambiguation5/5

    Tools are clearly separated by product prefix (confluence_ vs jira_) and have distinct actions on different resources (pages, issues, comments). No functional overlap between tools.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern with product prefixes (e.g., confluence_create_page, jira_add_comment). Minor inconsistencies: 'edit_confluence_page' vs 'update', and 'list_' versus '_list' patterns (e.g., list_confluence_pages vs jira_list_fields).

    Tool Count5/5

    22 tools split across two products (Confluence ~7, Jira ~15) is well-scoped. Each tool serves a clear purpose without excessive overlap or missing essential operations.

    Completeness4/5

    Core CRUD operations for Confluence pages and Jira issues are present, along with comments, search, transitions, and user lookup. Minor gaps like attachment upload are missing, but the surface covers primary workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers