atlassian-dc-mcp

Purpose: Connecting AI assistants to self-hosted Jira, Confluence, and Bitbucket Data Center instances.

Inferred · not functionally tested

Audience: developers and Atlassian Data Center administrators

Inferred · not functionally tested

Functions: agents, data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: WEB · deployment: browser, self_hosted, cli, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

atlassian-dc-mcp sits in PulseGate's Frameworks & runtimes category. Inferred · not functionally tested: It focuses on connecting AI assistants to self-hosted Jira, Confluence, and Bitbucket Data Center instances. Inferred · not functionally tested: It is built as an open-source project for developers and Atlassian Data Center administrators. Basis unknown · not verified: The project is open source (Open Source). Basis unknown · not verified: It ships for the web, the command line, and API, and it can be self-hosted.

It is developed by MrRefactoring. Inferred · not functionally tested: Among its 6 catalogued features are jira connectivity, confluence connectivity, and bitbucket connectivity. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.