MCP server that wraps the upstream [mcp-atlassian](https://github.com/sooperset/mcp-atlassian) toolset with browser-cookie authentication via
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. Exposed over MCP by the atlassian browser mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
You will need 5 environment variables: JIRA_URL, CONFLUENCE_URL, ATLASSIAN_USERNAME, ATLASSIAN_JIRA_LOGIN_URL, ATLASSIAN_CONFLUENCE_LOGIN_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by geiserx; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Atlassian Browser MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Variable | Description | Required |
|---|---|---|
| JIRA_URL | Endpoint or connection string the server talks to. | Yes |
| CONFLUENCE_URL | Endpoint or connection string the server talks to. | Yes |
| ATLASSIAN_USERNAME | Configuration value read at startup. | Optional |
| ATLASSIAN_JIRA_LOGIN_URL | Endpoint or connection string the server talks to. | Yes |
| ATLASSIAN_CONFLUENCE_LOGIN_URL | Endpoint or connection string the server talks to. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.