1. Conduid
  2. Social
  3. GeiserX/atlassian-browser-mcp
MCP server · Social

GeiserX/atlassian-browser-mcp

atlassian with Playwright SSO auth. Enables AI tools to access Atlassian Server/Data Center instances behind corporate SSO (Okta, SAML, ADFS) where API tokens are not available.

34Low

Scored 4 months ago · breakdown

About GeiserX/atlassian-browser-mcp

GeiserX/atlassian-browser-mcp is an MCP server in the Social category: atlassian with Playwright SSO auth. Enables AI tools to access Atlassian Server/Data Center instances behind corporate SSO (Okta, SAML, ADFS) where API tokens are not available. It has been installed 0 times through Conduid.

Install

Clone
git clone https://github.com/GeiserX/atlassian-browser-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about GeiserX/atlassian-browser-mcp

Powered by Claude · Grounded in docs

I know everything about GeiserX/atlassian-browser-mcp. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • ·Scoped permissionsNot checked yet.

README

atlassian-browser-mcp

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

Or configure as an MCP server in your editor (Cursor, Claude Code, etc.) pointing to the launcher script.

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
TOOLSETS all Which upstream toolsets to enable

Requirements

  • Python 3.12+
  • uv (for dependency management)
  • Chromium (installed automatically by Playwright)
  • Network access to your Atlassian instance

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About GeiserX/atlassian-browser-mcp

How do I install GeiserX/atlassian-browser-mcp?

Run git clone https://github.com/GeiserX/atlassian-browser-mcp, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is GeiserX/atlassian-browser-mcp safe to use with an AI agent?

Its trust score is 34 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is GeiserX/atlassian-browser-mcp still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.