MCP Atlassian
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Integrations
Provides integration with Atlassian products (Confluence and Jira), supporting both Atlassian Cloud and Server/Data Center deployments
Allows searching, creating, updating, and deleting Confluence pages, as well as retrieving comments and child pages
Enables searching, creating, updating, and managing Jira issues, including transitions, worklogs, and epic relationships
MCP Atlassian
Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). This integration supports both Confluence & Jira Cloud and Server/Data Center deployments.
Feature Demo
Compatibility
Product | Deployment Type | Support Status |
---|---|---|
Confluence | Cloud | ✅ Fully supported |
Confluence | Server/Data Center | ✅ Supported (version 7.9+) |
Jira | Cloud | ✅ Fully supported |
Jira | Server/Data Center | ✅ Supported (version 8.14+) |
Setup Guide
1. Authentication Setup
First, generate the necessary authentication tokens for Confluence & Jira:
For Cloud
- Go to https://id.atlassian.com/manage-profile/security/api-tokens
- Click Create API token, name it
- Copy the token immediately
For Server/Data Center
- Go to your profile (avatar) → Profile → Personal Access Tokens
- Click Create token, name it, set expiry
- Copy the token immediately
2. Installation
Choose one of these installation methods:
3. Configuration and Usage
You can configure the MCP server using command line arguments. The server supports using either Confluence, Jira, or both services - include only the arguments needed for your use case.
Required Arguments
For Cloud:
For Server/Data Center:
Note: You can configure just Confluence, just Jira, or both services. Simply include only the arguments for the service(s) you want to use. For example, to use only Confluence Cloud, you would only need
--confluence-url
,--confluence-username
, and--confluence-token
.
Optional Arguments
--transport
: Choose transport type (stdio
[default] orsse
)--port
: Port number for SSE transport (default: 8000)--[no-]confluence-ssl-verify
: Toggle SSL verification for Confluence Server/DC--[no-]jira-ssl-verify
: Toggle SSL verification for Jira Server/DC--confluence-spaces-filter
: Comma-separated list of space keys to filter Confluence search results (e.g., "DEV,TEAM,DOC")--jira-projects-filter
: Comma-separated list of project keys to filter Jira search results (e.g., "PROJ,DEV,SUPPORT")--read-only
: Run in read-only mode (disables all write operations)--verbose
: Increase logging verbosity (can be used multiple times, default is WARNING level)-v
or--verbose
: Set logging to INFO level-vv
or--verbose --verbose
: Set logging to DEBUG level
Note: All configuration options can also be set via environment variables. See the
.env.example
file in the repository for the full list of available environment variables.
IDE Integration
Claude Desktop Setup
Using uvx (recommended) - Cloud:
Note: Examples below use Cloud configuration. For Server/Data Center, use the corresponding arguments (--confluence-personal-token, --jira-personal-token) as shown in the Configuration section above.
Note: Examples below use Cloud configuration. For Server/Data Center, use the corresponding arguments (--confluence-personal-token, --jira-personal-token) as shown in the Configuration section above.
There are two ways to configure the Docker environment:
- Using cli arguments directly in the config:
- Using an environment file:
Cursor IDE Setup
- Open Cursor Settings
- Navigate to
Features
>MCP Servers
(or directly toMCP
) - Click
+ Add new global MCP server
This will create or edit the ~/.cursor/mcp.json
file with your MCP server configuration.
JSON Configuration for stdio Transport
For Cloud:
SSE Transport Configuration
For SSE transport, first start the server:
Then configure in Cursor:
Resources
Note: The MCP server filters resources to only show Confluence spaces and Jira projects that the user is actively interacting with, based on their contributions and assignments.
confluence://{space_key}
: Access Confluence spacesjira://{project_key}
: Access Jira projects
Available Tools
Tool | Description |
---|---|
confluence_search | Search Confluence content using CQL |
confluence_get_page | Get content of a specific Confluence page |
confluence_get_page_children | Get child pages of a specific Confluence page |
confluence_get_page_ancestors | Get parent pages of a specific Confluence page |
confluence_get_comments | Get comments for a specific Confluence page |
confluence_create_page | Create a new Confluence page |
confluence_update_page | Update an existing Confluence page |
confluence_delete_page | Delete an existing Confluence page |
jira_get_issue | Get details of a specific Jira issue |
jira_search | Search Jira issues using JQL |
jira_get_project_issues | Get all issues for a specific Jira project |
jira_create_issue | Create a new issue in Jira |
jira_update_issue | Update an existing Jira issue |
jira_delete_issue | Delete an existing Jira issue |
jira_get_transitions | Get available status transitions for a Jira issue |
jira_transition_issue | Transition a Jira issue to a new status |
jira_add_worklog | Add a worklog entry to a Jira issue |
jira_get_worklog | Get worklog entries for a Jira issue |
jira_link_to_epic | Link an issue to an Epic |
jira_get_epic_issues | Get all issues linked to a specific Epic |
Development & Debugging
Local Development Setup
If you've cloned the repository and want to run a local version:
For Cloud:
Debugging Tools
Security
- Never share API tokens
- Keep .env files secure and private
- See SECURITY.md for best practices
License
Licensed under MIT - see LICENSE file. This is not an official Atlassian product.
This server cannot be installed
Model Context Protocol (MCP) server for Atlassian Cloud products (Confluence and Jira). This integration is designed specifically for Atlassian Cloud instances and does not support Atlassian Server or Data Center deployments.