Atlassian MCP Servers
A monorepo of Model Context Protocol (MCP) servers for Atlassian products, built on FastMCP 3.
| Server | Tools | Package |
|---|---|---|
| Jira | 37 | atlassian-jira-mcp |
| Confluence | 41 | atlassian-confluence-mcp |
| Bitbucket | 44 | atlassian-bitbucket-mcp |
Structure
atlassian/
├── jira-mcp-server/ # Issues, boards, sprints, workflows
├── confluence-mcp-server/ # Pages, spaces, blogs, search
└── bitbucket-mcp-server/ # Repos, PRs, branches, builds
Installation
Each server is an independent Python package. Install from the server directory:
cd jira-mcp-server && pip install -e ".[dev]"
cd confluence-mcp-server && pip install -e ".[dev]"
cd bitbucket-mcp-server && pip install -e ".[dev]"
Requires Python 3.10+.
Authentication
All three servers support multiple authentication modes, auto-detected from environment variables.
Atlassian Cloud
Uses Basic auth with your email and an API token.
# Jira Cloud
export JIRA_MCP_URL=https://yoursite.atlassian.net
export JIRA_MCP_EMAIL=you@company.com
export JIRA_MCP_TOKEN=your-api-token
# Confluence Cloud
export CONFLUENCE_MCP_URL=https://yoursite.atlassian.net/wiki
export CONFLUENCE_MCP_EMAIL=you@company.com
export CONFLUENCE_MCP_TOKEN=your-api-token
# Bitbucket Cloud
export BITBUCKET_MCP_URL=https://api.bitbucket.org
export BITBUCKET_MCP_EMAIL=you@company.com
export BITBUCKET_MCP_TOKEN=your-app-password
Self-Hosted (Data Center)
Uses Bearer auth with a personal access token.
# Jira Data Center
export JIRA_MCP_URL=https://jira.company.com
export JIRA_MCP_TOKEN=your-personal-access-token
# Confluence Data Center
export CONFLUENCE_MCP_URL=https://confluence.company.com
export CONFLUENCE_MCP_TOKEN=your-personal-access-token
# Bitbucket Data Center
export BITBUCKET_MCP_URL=https://bitbucket.company.com
export BITBUCKET_MCP_TOKEN=your-personal-access-token
Self-Hosted (Username + Password)
The Jira server also supports traditional Basic authentication with username and password for older Server/Data Center instances:
export JIRA_MCP_URL=https://jira.company.com
export JIRA_MCP_USERNAME=your-username
export JIRA_MCP_PASSWORD=your-password
Auto-Detection
- If
EMAILis set: Cloud mode (Basic auth with email + API token) - If
USERNAME+PASSWORDare set (Jira only): Basic mode (Basic auth with credentials) - If only
TOKENis set: Data Center mode (Bearer auth with PAT) - Set
AUTH_TYPE=cloud,AUTH_TYPE=pat, orAUTH_TYPE=basicto override
MCP Client Configuration
Add to your .mcp.json (e.g., for Claude Code):
{
"mcpServers": {
"jira": {
"command": "atlassian-jira-mcp",
"env": {
"JIRA_MCP_URL": "https://yoursite.atlassian.net",
"JIRA_MCP_EMAIL": "you@company.com",
"JIRA_MCP_TOKEN": "your-api-token"
}
},
"confluence": {
"command": "atlassian-confluence-mcp",
"env": {
"CONFLUENCE_MCP_URL": "https://yoursite.atlassian.net/wiki",
"CONFLUENCE_MCP_EMAIL": "you@company.com",
"CONFLUENCE_MCP_TOKEN": "your-api-token"
}
},
"bitbucket": {
"command": "atlassian-bitbucket-mcp",
"env": {
"BITBUCKET_MCP_URL": "https://api.bitbucket.org",
"BITBUCKET_MCP_EMAIL": "you@company.com",
"BITBUCKET_MCP_TOKEN": "your-app-password"
}
}
}
}
Development
# Run tests (from any server directory)
pytest
# Lint
ruff check src/ tests/
# Type check
mypy src/
All servers enforce 100% test coverage.
License
MIT
Metadata
Release files for atlassian-jira-mcp 3.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| atlassian_jira_mcp-3.4.0.tar.gz | 54.7 kB | Without provenance | Details for atlassian_jira_mcp-3.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| atlassian_jira_mcp-3.4.0-py3-none-any.whl | Python 3 | none | any | Details for atlassian_jira_mcp-3.4.0-py3-none-any.whl |
Total release size: 90.9 kB
Release files / atlassian_jira_mcp-3.4.0.tar.gz
| Download URL | atlassian_jira_mcp-3.4.0.tar.gz |
|---|---|
| Size | 54.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d68ed7c905ae7ba42a8cdd0b2f14af1e5705691b09179591f75016f9763c05aa
|
|
BLAKE2b-256 checksum How to use checksums |
a7c6e652c6f86d2044ab5c734b2807fd4b62c13dcee00c4bf705142312432124
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / atlassian_jira_mcp-3.4.0-py3-none-any.whl
| Download URL | atlassian_jira_mcp-3.4.0-py3-none-any.whl |
|---|---|
| Size | 36.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
863545ff5df79299c2a0a538acfa83c8b131ccb8d480f9248b6feb3882f33ed9
|
|
BLAKE2b-256 checksum How to use checksums |
c69d1c449177d867f7f1d51203900bfc47ceaa15766325a9735d9386fb60a1c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for atlassian-jira-mcp 3.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.