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.
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
Add the server
bashclaude mcp add atlassian-browser-mcp -- uvx atlassian-browser-mcpVerify it's connected
bashclaude mcp listSharing 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).
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.
How to install Atlassian (browser SSO) in Claude DesktopDesktop app (MCP config)
Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this server
json{ "mcpServers": { "atlassian-browser-mcp": { "command": "uvx", "args": [ "atlassian-browser-mcp" ] } } }Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.
How to install Atlassian (browser SSO) in CursorAI-first code editor
Create / edit .cursor/mcp.json in your project
json{ "mcpServers": { "atlassian-browser-mcp": { "command": "uvx", "args": [ "atlassian-browser-mcp" ] } } }Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.
How to install Atlassian (browser SSO) in Codex CLIOpenAI coding agent
Add to ~/.codex/config.toml
toml[mcp_servers.atlassian-browser-mcp] command = "uvx" args = ["atlassian-browser-mcp"]Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.
How to install Atlassian (browser SSO) in WindsurfCodeium's agentic IDE
Edit ~/.codeium/windsurf/mcp_config.json
json{ "mcpServers": { "atlassian-browser-mcp": { "command": "uvx", "args": [ "atlassian-browser-mcp" ] } } }Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.
How to install Atlassian (browser SSO) in ClineVS Code autonomous agent
Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.
Add the server
json{ "mcpServers": { "atlassian-browser-mcp": { "command": "uvx", "args": [ "atlassian-browser-mcp" ] } } }
How to install Atlassian (browser SSO) in VS CodeCopilot / MCP support
Create .vscode/mcp.json
json{ "servers": { "atlassian-browser-mcp": { "type": "stdio", "command": "uvx", "args": [ "atlassian-browser-mcp" ] } } }Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.
What does Atlassian (browser SSO) need from you?
Configuration only — Declares config values but no credentials.
JIRA_URLoptionalEnvironment variableBase URL of the Jira Server/Data Center instance (set the one you use; Jira-only and Confluence-only setups work)
CONFLUENCE_URLoptionalEnvironment variableBase URL of the Confluence Server/Data Center instance
READ_ONLY_MODEoptionalEnvironment variableSet to true to hide every write tool (create, update, delete, transition, upload, restrictions)
ENABLED_TOOLSoptionalEnvironment variableComma-separated allow-list of tool names; unset exposes every tool
ATLASSIAN_BROWSER_AUTH_ENABLEDoptionalEnvironment variableSet to false to skip the browser session and use upstream token auth instead
ATLASSIAN_STORAGE_STATEoptionalEnvironment variablePath 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
Health score
A · 80Maintenance, 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 READMEatlassian-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_statustells 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-mcpFrom 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 serviceNeeds 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-mcpExcerpt — the full document is on GitHub.
Alternatives to Atlassian (browser SSO)
- Vibe Test — Browser Testing AgentA · 88Code-aware browser testing agent — 14 Playwright tools for AI code editors via MCP
- ai-browserA · 90Visible Electron browser driven by a semantic accessibility tree: 17 MCP tools, no screenshots.
- browser-automationB · 72Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real
- GitHub Platform Changelog — buy per-query in-session (githubchangelog)B · 65GitHub platform changelog feed. $0.01/query. Register in-session — free testnet funds.
Maintain Atlassian (browser SSO)? Add a badge to your README
Shows its health grade, and links readers to install steps for every client.
[](https://mcp-skills-hub.vercel.app/mcps/io-github-geiserx-atlassian-browser-mcp)Catalog data refreshed . Something wrong? Report it.