Home › Development › Atlassian (browser SSO)

Atlassian (browser SSO)

Jira and Confluence behind SSO via your own browser session: every mcp-atlassian tool, no API token

Python Cloud

★ 4 stars Last pushed 2026-11-11 License: GPL-3.0

View repository → Website →

Connect

Review any command before running it. Package names and URLs come from the server's own registry entry.

uvx atlassian-browser-mcp

Or add to your MCP client config:

{
  "mcpServers": {
    "atlassian-browser-mcp": {
      "command": "uvx",
      "args": [
        "atlassian-browser-mcp"
      ]
    }
  }
}

JIRA_URL — Base URL of the Jira Server/Data Center instance (set the one you use; Jira-only and Confluence-only setups work)
CONFLUENCE_URL — Base URL of the Confluence Server/Data Center instance
READ_ONLY_MODE — Set to true to hide every write tool (create, update, delete, transition, upload, restrictions)
ENABLED_TOOLS — Comma-separated allow-list of tool names; unset exposes every tool
ATLASSIAN_BROWSER_AUTH_ENABLED — Set to false to skip the browser session and use upstream token auth instead
MCP_ATLASSIAN_FILES_DIR — The only folder file tools read from (content_file, attachment uploads). Defaults to ~/.atlassian-browser-mcp/files; a filesystem root or a folder that contains your home directory is refused. Hold only files you are willing to publish, never this server's checkout or cookie jars
ATLASSIAN_STORAGE_STATE — Path of the saved browser session (cookie jar) written by atlassian-cli login; defaults to the current directory