Atlassian (browser SSO)
Jira and Confluence behind corporate SSO, using your browser session instead of tokens
- Pricing
- Open source
- Platforms
- CLI, macOS
- Runs
- Locally
- Version
- 1.5.1
- Listing updated
- today
Similar MCP servers
About Atlassian (browser SSO)
Atlassian (browser SSO) is an open-source MCP server for browser automation. It runs locally on your machine and is started by your AI client.
For teams on Atlassian Server or Data Center where SSO (Okta, SAML) blocks API tokens, this wraps the upstream mcp-atlassian toolset and authenticates with browser cookies captured through Playwright. You log in once per service using a bundled CLI; the server itself never opens a browser, so it never hangs waiting for one, and it returns an AuthRequiredError when cookies expire.
The README lists 63 Jira tools (38 read-only, 25 write) and 35 Confluence tools (20 read-only, 15 write), each carrying all four annotation hints so clients can auto-approve reads and confirm writes. READ_ONLY_MODE=true hides every write tool, and cookie jars are separate per host with mode 0600. On macOS it can reuse a live session from Chromium-family browsers, reading that browser's Keychain key and saying so on stderr.
Licensed GPL-3.0-or-later. MCP 2026-07-28 is not yet supported because upstream pins older libraries.
Install
Run in a terminal
claude mcp add atlassian-browser-mcp -- uvx atlassian-browser-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"atlassian-browser-mcp": {
"command": "uvx",
"args": [
"atlassian-browser-mcp"
]
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"atlassian-browser-mcp": {
"command": "uvx",
"args": [
"atlassian-browser-mcp"
]
}
}
}Add to .vscode/mcp.json
{
"servers": {
"atlassian-browser-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"atlassian-browser-mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"atlassian-browser-mcp": {
"command": "uvx",
"args": [
"atlassian-browser-mcp"
]
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"atlassian-browser-mcp": {
"command": "uvx",
"args": [
"atlassian-browser-mcp"
]
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
JIRA_URLBase URL of the Jira Server/Data Center instance (set the one you use; Jira-only and Confluence-only setups work)CONFLUENCE_URLBase URL of the Confluence Server/Data Center instanceREAD_ONLY_MODESet to true to hide every write tool (create, update, delete, transition, upload, restrictions)ENABLED_TOOLSComma-separated allow-list of tool names; unset exposes every toolATLASSIAN_BROWSER_AUTH_ENABLEDSet to false to skip the browser session and use upstream token auth insteadMCP_ATLASSIAN_FILES_DIRThe only folder file tools read from (content_file, attachment uploads). Defaults to ~/.atlassian-browser-mcp/files; a filesystem root or a folder that contains your home directory is refused. Hold only files you are willing to publish, never this server's checkout or cookie jarsATLASSIAN_STORAGE_STATEPath of the saved browser session (cookie jar) written by atlassian-cli login; defaults to the current directory
Tools this server provides (2)
Taken from the project documentation; the running server may differ.
- atlassian_auth_status
- Reports whether each service's saved session exists and works.
- atlassian_login
- Gives the atlassian-cli login command to show the user.
What it does
- SSO cookie auth
- Reuses a browser login instead of an API token.
- Full Jira and Confluence toolset
- Wraps every upstream mcp-atlassian tool.
- Read-only mode
- READ_ONLY_MODE hides all write tools.
- Auth status tool
- Tells an agent which service needs a login.
- Separate cookie jars
- Each host's cookies are stored apart with restrictive permissions.
Good for
- Searching Jira issues behind Okta SSO
- Reading Confluence pages without an API token
- Letting an agent transition tickets with confirmation
- Scripting issue and page lookups through the CLI
Pricing
Open source
GPL-3.0-or-later; free
More servers for the same service
Atlassian (browser SSO) FAQ
Why not use an API token?
On SSO-protected Server or Data Center instances tokens are often unavailable.
Does the server open a browser?
No. Login is a separate CLI step.
Can I make it read-only?
Yes, set READ_ONLY_MODE=true.
What does it require?
Python 3.11.5+, uv, Google Chrome and a display for the login.
Is Atlassian (browser SSO) free?
Yes. Atlassian (browser SSO) is open source, so you can use and self-host it for free.
How do I add Atlassian (browser SSO) to Claude Code?
Run this command in your terminal: claude mcp add atlassian-browser-mcp -- uvx atlassian-browser-mcp
What are the best alternatives to Atlassian (browser SSO)?
The closest alternatives to Atlassian (browser SSO) are REA, Browser Use, Scrapling MCP Server, Context7 and Chrome DevTools MCP.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.


