All MCP Servers
Dev Tools & GitMCP Registrypypi4 toolsA · 80

Atlassian (browser SSO) MCP server

io.github.GeiserX · Updated

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

At a glance

Atlassian (browser SSO) is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `uvx atlassian-browser-mcp`, and declares no required credentials. It exposes 4 tools, including atlassian_auth_status, atlassian_login and jira. It scores A (80/100) on the MCP Skills Hub health score as of Oct 27, 2026.

Source 3GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Atlassian (browser SSO) in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Atlassian (browser SSO) in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add atlassian-browser-mcp -- uvx atlassian-browser-mcp
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. atlassian_auth_status, atlassian_login, jira). It discovers them automatically.

What does Atlassian (browser SSO) need from you?

Configuration only — Declares config values but no credentials.

  • JIRA_URLoptionalEnvironment variable

    Base URL of the Jira Server/Data Center instance (set the one you use; Jira-only and Confluence-only setups work)

  • CONFLUENCE_URLoptionalEnvironment variable

    Base URL of the Confluence Server/Data Center instance

  • READ_ONLY_MODEoptionalEnvironment variable

    Set to true to hide every write tool (create, update, delete, transition, upload, restrictions)

  • ENABLED_TOOLSoptionalEnvironment variable

    Comma-separated allow-list of tool names; unset exposes every tool

  • ATLASSIAN_BROWSER_AUTH_ENABLEDoptionalEnvironment variable

    Set to false to skip the browser session and use upstream token auth instead

  • ATLASSIAN_STORAGE_STATEoptionalEnvironment variable

    Path of the saved browser session (cookie jar) written by atlassian-cli login; defaults to the current directory

Pass secrets through your shell environment rather than committing them into a config file.

What tools does Atlassian (browser SSO) expose? (4)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

  • atlassian_auth_statusWhether each service's saved session exists and works: jar age, cookie expiry, a live check, the next step
  • atlassian_loginThe exact `atlassian-cli login ` command to show the user
  • jiraEvery upstream Jira tool: issues, search, comments, transitions, sprints, boards, versions, links, worklogs, attachments, service desk, forms
  • confluenceEvery upstream Confluence tool: pages, search, comments, labels, attachments, history, templates, restrictions

What the code can do

Source analysis currently covers npm packages only. This server ships as a Python package, which needs a different parser.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit today — Actively maintained.
  • 3 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

A · 80

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 0 days ago.

  • Adoption20%18%

    3 stars.

  • Transparency20%100%

    4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.

  • Provenance15%75%

    Links to its own repository; package linkage unverified.

  • Packaging15%100%

    Publishes a pinned version (1.4.1).

Documentation

Full README

atlassian-browser-mcp

MCP server that wraps the upstream mcp-atlassian toolset with browser-cookie authentication via Playwright, for Atlassian Server/Data Center instances behind corporate SSO (Okta, SAML, etc.) where API tokens are not available. It runs locally over stdio: you log in once with the bundled CLI, and the server reuses the cookies.

Features

  • Every mcp-atlassian Jira and Confluence tool, authenticated with your SSO browser session instead of an API token, with upstream's own network hardening (SSRF redirect checks, DNS pinning, retries, rate limits, proxy and TLS settings) kept in force.
  • One login per service with the CLI; the server itself never opens a browser, so it never hangs waiting for one.
  • atlassian_auth_status tells an agent which service needs a login before it fails mid-task.
  • Optional one-time seeding of the automation profile from your real Chrome profile (ATLASSIAN_SEED_FROM_CHROME_PROFILE), so the first login is often one click.
  • On macOS, reuses a live session from an installed Chromium-family browser (Arc, Brave, Edge, Chrome and others) without opening a window. It reads that browser's Keychain key, says so on stderr, and can be turned off.
  • Separate cookie jars for Jira and Confluence, holding only that host's cookies, mode 0600. Jira-only or Confluence-only setups work.
  • A command-line front-end (atlassian-cli) for scripts and agents: get and search issues and pages.
  • Falls back to token auth with ATLASSIAN_BROWSER_AUTH_ENABLED=false.

Quick start

From PyPI, with uv installed:

bash
JIRA_URL=https://jira.example.com uvx --from atlassian-browser-mcp atlassian-cli login jira   # once per service, opens your browser
CONFLUENCE_URL=https://confluence.example.com uvx --from atlassian-browser-mcp atlassian-cli login confluence
JIRA_URL=https://jira.example.com CONFLUENCE_URL=https://confluence.example.com uvx atlassian-browser-mcp

From a checkout, with the exact versions in uv.lock:

bash
git clone https://github.com/GeiserX/atlassian-browser-mcp.git && cd atlassian-browser-mcp
UV_PROJECT_ENVIRONMENT=.venv-atlassian-browser uv sync --frozen   # installs the versions in uv.lock
JIRA_URL=https://jira.example.com CONFLUENCE_URL=https://confluence.example.com ./atlassian-cli login jira   # once per service

Needs Python 3.11+, uv, Google Chrome and a display for the login. The server never opens a browser window. It reads the saved cookies; when they are missing or expired it returns an AuthRequiredError asking you to run the login again, and on macOS it also looks for a live session in your installed browsers in the background, so a retry a few seconds later may already work. Seeding from Chrome and every setting are in Getting started.

Add it to your client

Every client runs the server over stdio. Set only the URL of a service you use. The examples use the PyPI package through uvx; from a checkout, replace uvx atlassian-browser-mcp with /path/to/atlassian-browser-mcp/run-atlassian-browser-mcp.sh.

Claude Code

bash
claude mcp add --transport stdio atlassian \
  --env JIRA_URL=https://jira.example.com \
  --env CONFLUENCE_URL=https://confluence.example.com \
  -- uvx atlassian-browser-mcp

Excerpt — the full document is on GitHub.

Maintain Atlassian (browser SSO)? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![Atlassian (browser SSO) on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-geiserx-atlassian-browser-mcp)](https://mcp-skills-hub.vercel.app/mcps/io-github-geiserx-atlassian-browser-mcp)

Catalog data refreshed . Something wrong? Report it.