Jira Cloud MCP
Native async Python MCP server for Jira Cloud REST API v3 and Jira Server/Data Center REST API v2. Cloud uses JIRA_EMAIL + JIRA_TOKEN; Data Center uses JIRA_PERSONAL_TOKEN or JIRA_USERNAME + JIRA_PASSWORD.
Configure the matching variables and run:
uv sync
uv run jira-mcp
The URL determines the API mode automatically: *.atlassian.net uses Cloud endpoints, while other hosts use Data Center endpoints. Exposes JQL search, issue CRUD, comments, transitions, assignment, project, and issue-type tools. Jira descriptions and comments use ADF in Cloud and wiki markup strings in Data Center. Build with uv build; publish with UV_PUBLISH_TOKEN=pypi-... uv publish. The package name is jira-mcp-atlassian.
1 maintainer
Metadata
1 maintainer
Release files for jira-mcp-atlassian 0.2.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 |
|---|---|---|---|---|
| jira_mcp_atlassian-0.2.0.tar.gz | 5.0 kB | With provenance | Details for jira_mcp_atlassian-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jira_mcp_atlassian-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for jira_mcp_atlassian-0.2.0-py3-none-any.whl |
Total release size: 10.8 kB
Release files / jira_mcp_atlassian-0.2.0.tar.gz
| Download URL | jira_mcp_atlassian-0.2.0.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3e1ba241c60d077a0e37ad26869e1e9e7a9a98ab1d09193f9d22810e55cde7d
|
|
BLAKE2b-256 checksum How to use checksums |
51b4857e6a21966f450b33e6d3b1de40cc8037257e73ff63b078dd85dad158b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logRelease files / jira_mcp_atlassian-0.2.0-py3-none-any.whl
| Download URL | jira_mcp_atlassian-0.2.0-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
571361088224c81633e7184d6267276673bc5f5a867492601068cb65063b8c67
|
|
BLAKE2b-256 checksum How to use checksums |
ec8e8198069aff436a94939a286dc6687b0adada3a856b809497f7cbc252bafb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logSecurity for jira-mcp-atlassian 0.2.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for jira_mcp_atlassian-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logA 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.
