A previous release had provenance metadata, but this release does not. View details.
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 dual 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
Auto-Detection
- If
EMAILis set: Cloud mode (Basic auth) - If only
TOKENis set: Data Center mode (Bearer auth) - Set
AUTH_TYPE=cloudorAUTH_TYPE=patto 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-bitbucket-mcp 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| atlassian_bitbucket_mcp-1.4.0.tar.gz | 28.4 kB | Without provenance | Details for atlassian_bitbucket_mcp-1.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| atlassian_bitbucket_mcp-1.4.0-py3-none-any.whl | Python 3 | none | any | Details for atlassian_bitbucket_mcp-1.4.0-py3-none-any.whl |
Total release size: 45.4 kB
Release files / atlassian_bitbucket_mcp-1.4.0.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | atlassian_bitbucket_mcp-1.4.0.tar.gz |
|---|---|
| Size | 28.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ff958279b5216c67f378567913752aa2d9e5e20034b1b3dc68a2eb1a6a93abe
|
|
BLAKE2b-256 checksum How to use checksums |
b7ed3749d4b43338d59903758c9608b9bea31eeee164770521290d2fa0eaafcd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / atlassian_bitbucket_mcp-1.4.0-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | atlassian_bitbucket_mcp-1.4.0-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9c062aed83429174463b046bc1b5d95abf9258be5a8342e560b350c1049a1a69
|
|
BLAKE2b-256 checksum How to use checksums |
0c15d3a3954367a18d59dcc4dc37b65d153a596d87328ed0bd8f0443737d820a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for atlassian-bitbucket-mcp 1.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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 1.0.0 2 files With provenance
- Added 1.4.0 2 files Without provenance
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.