Atlassian (browser SSO)

Name: Atlassian (browser SSO)
Author: GeiserX

by GeiserXversion 1.4.1i★ –iRuns on your computer

Registry nameio.github.GeiserX/atlassian-browser-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: JIRA_URL, CONFLUENCE_URL, READ_ONLY_MODE, ENABLED_TOOLS, ATLASSIAN_BROWSER_AUTH_ENABLED, ATLASSIAN_STORAGE_STATE

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "atlassian-browser": {
      "command": "uvx",
      "args": [
        "atlassian-browser-mcp"
      ],
      "env": {
        "JIRA_URL": "your-value",
        "CONFLUENCE_URL": "your-value",
        "READ_ONLY_MODE": "your-value",
        "ENABLED_TOOLS": "your-value",
        "ATLASSIAN_BROWSER_AUTH_ENABLED": "your-value",
        "ATLASSIAN_STORAGE_STATE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add atlassian-browser --env JIRA_URL=your-value --env CONFLUENCE_URL=your-value --env READ_ONLY_MODE=your-value --env ENABLED_TOOLS=your-value --env ATLASSIAN_BROWSER_AUTH_ENABLED=your-value --env ATLASSIAN_STORAGE_STATE=your-value -- uvx atlassian-browser-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "atlassian-browser": {
      "command": "uvx",
      "args": [
        "atlassian-browser-mcp"
      ],
      "env": {
        "JIRA_URL": "your-value",
        "CONFLUENCE_URL": "your-value",
        "READ_ONLY_MODE": "your-value",
        "ENABLED_TOOLS": "your-value",
        "ATLASSIAN_BROWSER_AUTH_ENABLED": "your-value",
        "ATLASSIAN_STORAGE_STATE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "atlassian-browser": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "atlassian-browser-mcp"
      ],
      "env": {
        "JIRA_URL": "your-value",
        "CONFLUENCE_URL": "your-value",
        "READ_ONLY_MODE": "your-value",
        "ENABLED_TOOLS": "your-value",
        "ATLASSIAN_BROWSER_AUTH_ENABLED": "your-value",
        "ATLASSIAN_STORAGE_STATE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

JIRA_URL env
Base URL of the Jira Server/Data Center instance (set the one you use; Jira-only and Confluence-only setups work)
CONFLUENCE_URL env
Base URL of the Confluence Server/Data Center instance
READ_ONLY_MODE env
Set to true to hide every write tool (create, update, delete, transition, upload, restrictions)
ENABLED_TOOLS env
Comma-separated allow-list of tool names; unset exposes every tool
ATLASSIAN_BROWSER_AUTH_ENABLED env
Set to false to skip the browser session and use upstream token auth instead
ATLASSIAN_STORAGE_STATE env
Path of the saved browser session (cookie jar) written by atlassian-cli login; defaults to the current directory

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account GeiserX, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

More stars than 0% of the other 881 servers in this category
Published to the registry more recently than 77% of the other 881 servers in this category
Basic checks equal to or better than 100% of the other 881 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Atlassian (browser SSO) safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.4.1) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 17 days ago

Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 16 days ago

Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

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:

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

claude mcp add --transport stdio atlassian \

--env JIRA_URL=https://jira.example.com \ --env CONFLUENCE_URL=https://confluence.example.com \ -- uvx atlassian-browser-mcp

Claude Desktop (claude_desktop_config.json) and Cursor (~/.cursor/mcp.json or .cursor/mcp.json)

"mcpServers": { "atlassian": { "command": "uvx", "args": ["atlassian-browser-mcp"], "env": { "JIRA_URL": "https://jira.example.com", "CONFLUENCE_URL": "https://confluence.example.com" } } } }

VS Code (.vscode/mcp.json)

"servers": { "atlassian": { "type": "stdio", "command": "uvx", "args": ["atlassian-browser-mcp"], "env": { "JIRA_URL": "https://jira.example.com", "CONFLUENCE_URL": "https://confluence.example.com" } } } }

Codex (~/.codex/config.toml)

[mcp_servers.atlassian]

command = "uvx" args = ["atlassian-browser-mcp"] env = { JIRA_URL = "https://jira.example.com", CONFLUENCE_URL = "https://confluence.example.com" }

Protocol. Speaks MCP 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05 over stdio, which covers clients that open with an initialize handshake (Claude Code, Claude Desktop, Cursor and VS Code today). MCP 2026-07-28 is not supported yet: upstream mcp-atlassian pins mcp<2 and fastmcp<4 (https://github.com/sooperset/mcp-atlassian/issues/1541), and this server follows as soon as upstream moves. It runs on stdio only and refuses to start with any other FASTMCP_TRANSPORT.

Read-only mode

Write tools act as you, with your SSO identity. To hide all of them (create, update, delete, transition, upload, restrictions), set READ_ONLY_MODE=true in the server's env. Upstream enforces it when listing and when calling. ENABLED_TOOLS (a comma-separated allow-list of tool names) and TOOLSETS narrow the list further; see Configuration.

Tools

Tool	What it does	Hints
`atlassian_auth_status`	Whether each service's saved session exists and works: jar age, cookie expiry, a live check, the next step	read-only
`atlassian_login`	The exact `atlassian-cli login` command to show the user	read-only
`jira_*` (63)	Every upstream Jira tool: issues, search, comments, transitions, sprints, boards, versions, links, worklogs, attachments, service desk, forms	38 read-only, 25 write
`confluence_*` (35)	Every upstream Confluence tool: pages, search, comments, labels, attachments, history, templates, restrictions	20 read-only, 15 write

Every tool carries a title and all four annotation hints (read-only, destructive, idempotent, open-world), so clients can auto-approve reads and confirm writes. The full list and the CLI are in Usage.

Documentation

Getting started: requirements, install, the first login, seeding from Chrome, the MCP client config
Configuration: every environment variable and its default
Usage: the MCP tools and the CLI commands
How it works: why login and serving are separate processes, and the files
Troubleshooting: symptoms, causes, fixes, and what to put in a bug report

License

GPL-3.0-or-later

Atlassian (browser SSO)

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Web & browsersi

Common questions

Alternatives

Browser Use

Chrome DevTools MCP

MCP Server Browser

README from the maker

atlassian-browser-mcp

Features

Quick start

Add it to your client

Read-only mode

Tools

Documentation

License