Back to Browse

Atlassian Browser MCP Server

Developer ToolsUse Caution4.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Jira and Confluence behind SSO via your own browser session: every mcp-atlassian tool, no API token

About

Jira and Confluence behind SSO via your own browser session: every mcp-atlassian tool, no API token

Security Report

4.2
Use Caution4.2High Risk

This is a legitimate Atlassian Jira and Confluence wrapper that authenticates with the user's own SSO browser cookies and keeps upstream's network hardening in place. The main concern is the optional macOS feature that reads installed browsers' Keychain keys and cookies, which is a sensitive capability even though it is disclosed and can be turned off. The auth helper module was truncated, so its cookie-harvesting code could not be fully reviewed. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 4 high severity). Package verification found 1 issue.

5 files analyzed · 11 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

env_vars

Check that this permission is expected for this type of plugin.

process_spawn

Check that this permission is expected for this type of plugin.

browser_cookies

Check that this permission is expected for this type of plugin.

keychain_access

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Base URL of the Jira Server/Data Center instance (set the one you use; Jira-only and Confluence-only setups work)Optional

Environment variable: JIRA_URL

Base URL of the Confluence Server/Data Center instanceOptional

Environment variable: CONFLUENCE_URL

Set to true to hide every write tool (create, update, delete, transition, upload, restrictions)Optional

Environment variable: READ_ONLY_MODE

Comma-separated allow-list of tool names; unset exposes every toolOptional

Environment variable: ENABLED_TOOLS

Set to false to skip the browser session and use upstream token auth insteadOptional

Environment variable: ATLASSIAN_BROWSER_AUTH_ENABLED

The 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 jarsOptional

Environment variable: MCP_ATLASSIAN_FILES_DIR

Path of the saved browser session (cookie jar) written by atlassian-cli login; defaults to the current directoryOptional

Environment variable: ATLASSIAN_STORAGE_STATE

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "atlassian-browser-mcp": {
      "command": "uvx",
      "args": [
        "atlassian-browser-mcp==1.5.0"
      ],
      "env": {
        "JIRA_URL": "your-jira-url-here",
        "ENABLED_TOOLS": "your-enabled-tools-here",
        "CONFLUENCE_URL": "your-confluence-url-here",
        "READ_ONLY_MODE": "your-read-only-mode-here",
        "ATLASSIAN_STORAGE_STATE": "your-atlassian-storage-state-here",
        "MCP_ATLASSIAN_FILES_DIR": "your-mcp-atlassian-files-dir-here",
        "ATLASSIAN_BROWSER_AUTH_ENABLED": "your-atlassian-browser-auth-enabled-here"
      }
    }
  }
}

Some servers take additional arguments. See the repository for details.

Reviews

No reviews yet

Be the first to review this server!