home / mcp / atlassian mcp server

Atlassian MCP Server

Provides real-time access to Jira, Compass, and Confluence data through secure OAuth 2.1, enabling search, summarization, and content creation from MCP clients.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "atlassian-atlassian-mcp-server": {
      "url": "https://mcp.atlassian.com/v1/mcp"
    }
  }
}

You install and run the Atlassian MCP Server to securely connect your Atlassian Cloud data (Jira, Compass, and Confluence) with compatible external tools. This cloud-based bridge lets you search, summarize, create, and update content across Atlassian apps in real time, while enforcing your existing permissions through OAuth 2.1 and token scoping.

How to use

Use an MCP client from your preferred tool or IDE to connect to the server and begin interacting with Jira, Compass, and Confluence data. After connection, you can search for content, summarize pages or plans, and perform actions such as creating or updating issues and pages based on natural language commands. You can automate repetitive tasks like turning meeting notes into Jira tickets or converting specifications into new pages.

How to install

# Prerequisites
# Ensure you have Node.js v18 or later installed
node -v

# Install and run the MCP server if you are using a containerized/standard release flow (respect any official deployment guide you have).
# Example placeholder steps; use your organization’s official MCP server deployment commands where provided.

# 1) Authenticate and set up the MCP server (exact commands depend on your environment)
# 2) Start the MCP server (the following is a placeholder for the standard start flow)

Additional sections

Configuration and security specifics are focused on ensuring secure access, proper data permissions, and compliance with your Atlassian Cloud settings. The server uses HTTPS with TLS 1.2 or later and OAuth 2.1 to authorize client actions. Access respects Jira, Compass, and Confluence permissions, and IP allowlists are honored for tool calls routed through the MCP server.

Security

Security is a central concern. Always use trusted MCP clients and servers, limit the scope of tokens, and require human confirmation for high-impact actions. Monitor audit logs for unusual activity and review risk guidance related to MCP usage to maintain a strong security posture.

Troubleshooting

If you encounter authorization or IP allowlisting issues, verify that the correct MCP scopes are requested during the 3LO consent flow and confirm that your IP ranges are allowed for the relevant Atlassian apps. Check that you are using the right Atlassian account and site, and ensure the MCP server is configured with the appropriate permissions.

Notes

The MCP server architecture enables real-time data streaming from Atlassian apps to supported clients. Permissions, scope, and session handling are enforced according to your Atlassian Cloud configuration to ensure actions align with your access controls.

Available tools

search_jira_compass_confluence

Search across Jira, Compass, and Confluence content from an MCP client to surface relevant issues, pages, and plans without leaving your current tool.

summarize_content

Summarize Jira issues, Confluence pages, or Compass components to provide concise overviews within your workflow.

create_update_issues

Create new Jira issues or update existing ones using natural language commands issued through a connected MCP client.

create_update_pages

Create or update Confluence pages or Compass content via MCP-enabled clients using descriptive prompts.

automate_workflows

Automate repetitive tasks such as generating Jira tickets from meeting notes or specifications.