Atlassian Browser Mcp

atlassian-browser-mcp

[](LICENSE) [](https://python.org) [](https://github.com/GeiserX/atlassian-browser-mcp/stargazers) [](https://github.com/sooperset/mcp-atlassian) [](https://glama.ai/mcp/servers/GeiserX/atlassian-browser-mcp)

MCP server that wraps the upstream [mcp-atlassian](https://github.com/sooperset/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

Authentication and serving are **two separate processes** — this is what keeps the MCP server from hanging:

1. Authenticate with the CLI (foreground, where a browser can open): atlassian-cli login runs Playwright, you complete SSO/MFA once, and cookies are saved to a per-service storage-state file.
2. The MCP server serves data only. It reads the saved cookies via a custom requests.Session subclass and never opens a browser. On a missing/expired session it fails fast with an AuthRequiredError telling you to run the CLI login — it does not block waiting for an interactive login.

⚠️ Earlier versions launched the login browser from inside the server. Because the server is detached and async, that blocked tool calls for minutes (often forever) and could deadlock Playwright's