Atlassian (local) logo

Atlassian (local)

Beta

A community-maintained Jira and Confluence server that reads and writes issues, pages and comments with a user's API token. It is not published by Atlassian.

  • Productivity
  • Local
Runs
On the developer's Mac
Launched with
uvx, Docker
Platform
macOS
Publisher
Community (sooperset)

How it works

Every agent request passes through Ferentin policy before it reaches Atlassian (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with uvx mcp-atlassian or docker run -i --rm ghcr.io/sooperset/mcp-atlassian.

Ferentin's endpoint agent finds Atlassian (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Atlassian (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Atlassian (local)

A community-maintained Jira and Confluence server that reads and writes issues, pages and comments with a user's API token. It is not published by Atlassian.

Frequently asked about Atlassian (local)

How do I connect Atlassian (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Atlassian (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Atlassian (local) integration generally available?
The Atlassian (local) integration is currently beta on Ferentin.