Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
MCP server for Jira and Confluence tools
This server exposes Jira and Confluence actions through the Model Context Protocol, so your agent can search, read, create, and update Atlassian content. It supports Cloud and Server/Data Center deployments and documents both local and HTTP transport setups.
Builders who want their agent to read and update Jira tickets and Confluence pages from the same workflow.
You can manage Atlassian work through your agent instead of switching between browser tabs and manual copy-paste.
What it does
Jira tools
Search issues with JQL, get issue details, create issues, update issues, and transition status.
Confluence tools
Search pages with CQL, fetch page content, create pages, update pages, and add comments.
Cloud and Server/Data Center support
Works with Atlassian Cloud and with Server/Data Center deployments, with different auth options for each.
Multiple transport options
Documents local use through `uvx`, plus HTTP transport options like SSE and streamable HTTP.
Documentation and troubleshooting
Includes setup, authentication, configuration, compatibility, tool reference, and troubleshooting docs.
How to get it
- 1Use the same uvx server with your Atlassian credentials
autohand mcp add mcp-atlassian env \ JIRA_URL=https://your-company.atlassian.net \ JIRA_USERNAME=your.email@company.com \ JIRA_API_TOKEN=your_api_token \ CONFLUENCE_URL=https://your-company.atlassian.net/wiki \ CONFLUENCE_USERNAME=your.email@company.com \ CONFLUENCE_API_TOKEN=your_api_token \ uvx mcp-atlassian
README
MCP Atlassian
Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Supports both Cloud and Server/Data Center deployments.
https://github.com/user-attachments/assets/35303504-14c6-4ae4-913b-7c25ea511c3e
Quick Start
1. Get Your API Token
Go to https://id.atlassian.com/manage-profile/security/api-tokens and create a token.
For Server/Data Center, use a Personal Access Token instead. See Authentication.
2. Configure Your IDE
Add to your Claude Desktop or Cursor MCP configuration:
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": ["mcp-atlassian"],
"env": {
"JIRA_URL": "https://your-company.atlassian.net",
"JIRA_USERNAME": "your.email@company.com",
"JIRA_API_TOKEN": "your_api_token",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "your.email@company.com",
"CONFLUENCE_API_TOKEN": "your_api_token"
}
}
}
}
Server/Data Center users: Use
JIRA_PERSONAL_TOKENinstead ofJIRA_USERNAME+JIRA_API_TOKEN. See Authentication for details.
Autohand Code
Use the same uvx server with your Atlassian credentials:
autohand mcp add mcp-atlassian env \
JIRA_URL=https://your-company.atlassian.net \
JIRA_USERNAME=your.email@company.com \
JIRA_API_TOKEN=your_api_token \
CONFLUENCE_URL=https://your-company.atlassian.net/wiki \
CONFLUENCE_USERNAME=your.email@company.com \
CONFLUENCE_API_TOKEN=your_api_token \
uvx mcp-atlassian
Add --scope project after add to keep the configuration in the current
project. See Autohand Code for current
installation and CLI details.
3. Start Using
Ask your AI assistant to:
- "Find issues assigned to me in PROJ project"
- "Search Confluence for onboarding docs"
- "Create a bug ticket for the login issue"
- "Update the status of PROJ-123 to Done"
Documentation
Full documentation is available at mcp-atlassian.soomiles.com.
Documentation is also available in llms.txt format, which LLMs can consume easily:
llms.txt— documentation sitemapllms-full.txt— complete documentation
| Topic | Description |
|---|---|
| Installation | uvx, Docker, pip, from source |
| Authentication | API tokens, PAT, OAuth 2.0 |
| Configuration | IDE setup, environment variables |
| HTTP Transport | SSE, streamable-http, multi-user |
| Tools Reference | All Jira & Confluence tools |
| Troubleshooting | Common issues & debugging |
Compatibility
| Product | Deployment | Support |
|---|---|---|
| Confluence | Cloud | Fully supported |
| Confluence | Server/Data Center | Supported (v6.0+) |
| Jira | Cloud | Fully supported |
| Jira | Server/Data Center | Supported (v8.14+) |
Key Tools
| Jira | Confluence |
|---|---|
jira_search - Search with JQL | confluence_search - Search with CQL |
jira_get_issue - Get issue details | confluence_get_page - Get page content |
jira_create_issue - Create issues | confluence_create_page - Create pages |
jira_update_issue - Update issues | confluence_update_page - Update pages |
jira_transition_issue - Change status | confluence_add_comment - Add comments |
98 tools total — See Tools Reference for the complete list.
Security
Never share API tokens. Keep .env files secure. See SECURITY.md.
Contributing
See CONTRIBUTING.md for development setup.
License
MIT - See LICENSE. Not an official Atlassian product.
Files in the repo
- .claude
- .devcontainer
- .github
- docs
- helm
- scripts
- src
- tests
- .dockerignore
- .env.example
- .gitignore
- .mintignore
- .pre-commit-config.yaml
- .worktreeinclude
- AGENTS.md
- CLAUDE.md
- CONTRIBUTING.md
- Dockerfile
- docs.json
- LICENSE
- pyproject.toml
- README.md
- SECURITY.md
- smithery.yaml
- uv.lock
Discussion (0)
Ask about usage, or say what you built with itSign in to join the discussion.
No comments yet. Be the first to say what this is good for.
More connectors
High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 158 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

Universal provider proxy for OpenAI Codex & Claude Code — use any LLM (Claude, Gemini, Grok, DeepSeek, Ollama…) with Codex CLI, App, SDK, and Claude Code
Git-native persistent memory for AI coding agents. Implements Google OKF v0.2 with sub-300µs in-memory BM25 search, embedded MCP server, and progressive disclosure. Slashes token bloat by 80% with zero external databases or dependencies. Built in pure Go.
Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo workflows.
Stop your AI from making things up — it proposes, deterministic tools decide, every claim checked against ground truth with evidence. Grounded facts and context survive resets. Reverse engineering is the proving ground. MCP server + CLI.