atlassian-browser-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | Jira base URL (e.g. https://yourco.atlassian.net) | |
| TOOLSETS | No | Which upstream toolsets to enable | all |
| CONFLUENCE_URL | Yes | Confluence base URL (e.g. https://yourco.atlassian.net). For Cloud (*.atlassian.net) the /wiki context path is appended automatically | |
| ATLASSIAN_SSO_MARKERS | No | Comma-separated URL/text markers for SSO redirect detection. Defaults cover Okta, ADFS, Azure AD, PingOne, Google SAML | |
| ATLASSIAN_STORAGE_STATE | No | Cookie-jar file. Per-service by default; an explicit value is still namespaced per service | ./.atlassian-browser-state-{service}.json |
| ATLASSIAN_BROWSER_USER_AGENT | No | Custom User-Agent string for API requests and liveness probes | Chrome 136 |
| ATLASSIAN_BROWSER_AUTH_ENABLED | No | Enable browser-cookie auth (set false to fall back to token auth) | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| atlassian_loginA | Report how to authenticate. Cookies are captured OUT-OF-BAND. This tool intentionally does NOT open a browser or drive Playwright (removed entirely): a sync browser login inside the async-dispatched MCP server deadlocks the event loop and hung the server. Instead, capture cookies with the Chrome extension (chrome-extension/) and load them via the CLI: Once the jar is saved, the server's tools reuse it automatically — no browser is ever opened from within the server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tinyc0der/atlassian-cookie-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server