Skip to main content
Glama
deenesjakoruzh
GeiserX

atlassian-browser-mcp

by GeiserX
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

atlassian-browser-mcp

License: GPL-3.0 Python 3.11+ GitHub stars mcp-atlassian GeiserX/atlassian-browser-mcp MCP server

MCP server that wraps the upstream mcp-atlassian toolset with browser-cookie authentication via Playwright. Designed for Atlassian Server/Data Center instances behind corporate SSO (Okta, SAML, etc.) where API tokens are not available.

How it works

  1. On first use (or when the session expires), Playwright opens a real Chromium window for manual SSO/MFA

  2. After login, cookies are saved to a Playwright storage-state file

  3. All subsequent MCP tool calls use those cookies via a custom requests.Session subclass

  4. If an API response looks like an SSO redirect, the browser reopens automatically

The server monkey-patches JiraClient and ConfluenceClient constructors in mcp-atlassian to inject the browser-backed session, giving full parity with the upstream tool surface (72 tools + 1 atlassian_login helper = 73 total).

Files

File

Purpose

atlassian_browser_mcp_full.py

Entrypoint. Patches upstream clients, registers atlassian_login tool, runs the MCP server

atlassian_browser_auth.py

Shared auth: BrowserCookieSession, interactive_login(), SSO detection

run-atlassian-browser-mcp.sh

Launcher: creates venv, installs deps via uv, runs compatibility check, starts server

pyproject.toml

Dependency pins

Usage

./run-atlassian-browser-mcp.sh

MCP server configuration

Add to your Claude Code, Cursor, or other MCP client configuration:

{
  "mcpServers": {
    "atlassian": {
      "command": "/path/to/atlassian-browser-mcp/run-atlassian-browser-mcp.sh",
      "env": {
        "JIRA_URL": "https://jira.example.com",
        "CONFLUENCE_URL": "https://confluence.example.com",
        "ATLASSIAN_USERNAME": "your.email@company.com"
      }
    }
  }
}

On first use (or when cookies expire), a Chromium window opens for SSO login. After login completes, the browser closes automatically and all MCP tool calls proceed using the saved session.

Environment variables

Variable

Default

Description

JIRA_URL

(required)

Jira base URL (e.g. https://jira.example.com)

CONFLUENCE_URL

(required)

Confluence base URL (e.g. https://confluence.example.com)

ATLASSIAN_BROWSER_AUTH_ENABLED

true

Enable browser auth (set false to fall back to token auth)

ATLASSIAN_BROWSER_PROFILE_DIR

./.atlassian-browser-profile

Persistent Chromium profile directory

ATLASSIAN_STORAGE_STATE

./.atlassian-browser-state.json

Playwright storage-state file

ATLASSIAN_LOGIN_TIMEOUT_SECONDS

300

Seconds to wait for manual login

ATLASSIAN_USERNAME

(none)

Optional: prefill username on SSO page

ATLASSIAN_SSO_MARKERS

(auto)

Comma-separated URL/text markers for SSO redirect detection. Defaults cover Okta, ADFS, Azure AD, PingOne, Google SAML

ATLASSIAN_BROWSER_CHANNEL

chromium

Browser channel (chromium, chrome, msedge)

ATLASSIAN_JIRA_LOGIN_URL

{JIRA_URL}/secure/Dashboard.jspa

Override the Jira login entry point URL

ATLASSIAN_CONFLUENCE_LOGIN_URL

{CONFLUENCE_URL}

Override the Confluence login entry point URL

ATLASSIAN_BROWSER_USER_AGENT

(Chrome 136)

Custom User-Agent string for API requests

TOOLSETS

all

Which upstream toolsets to enable

Requirements

  • Python 3.11+

  • uv (for dependency management)

  • Chromium (installed automatically by Playwright)

  • A graphical display (macOS, X11, or Wayland) — required for interactive SSO login

  • Network access to your Atlassian instance

Troubleshooting

Symptom

Cause

Fix

Browser doesn't open

Headless environment (SSH, Docker)

Forward X11 or run initial login on a machine with a display

Login timed out

Didn't land on Jira/Confluence URL within 300s

Check JIRA_URL/CONFLUENCE_URL match exactly where your IdP redirects after login. Increase ATLASSIAN_LOGIN_TIMEOUT_SECONDS if needed

Tools return HTML instead of JSON

Session expired, SSO markers not matching your IdP

Set ATLASSIAN_SSO_MARKERS with your IdP's URL pattern

"Upstream compatibility check failed"

mcp-atlassian version changed its internal API

Pin to a compatible version or update the wrapper

"Executable doesn't exist"

Playwright Chromium not installed

Run python -m playwright install chromium

Install Server
A
license - permissive license
A
quality
B
maintenance

How are these scores calculated?

Maintenance

–Maintainers
–Response time
–Release cycle
1Releases (12mo)

Resources

Tools

View all tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GeiserX/atlassian-browser-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server