| FMRS | 57 / 100 · C | 66 / 100 · C |
|---|
| Reliability | 8 / 20 | 8 / 20 |
|---|
| Security and permissions | 8 / 20 | 15 / 20 |
|---|
| Maintenance | 13 / 20 | 15 / 20 |
|---|
| Documentation | 16 / 20 | 15 / 20 |
|---|
| Setup experience | 12 / 20 | 13 / 20 |
|---|
| Best for | - Developers blocked by OAuth app registration or admin approval
- Users across Claude Code, Cursor, Copilot, Windsurf, Gemini CLI, and Codex CLI
- Self-hosters who want tokens and data kept local
| - Developers, content creators, and project teams using Atlassian Cloud
- Teams that want Atlassian access inside ChatGPT, Claude, Cursor, or VS Code
- Users who need natural-language search, write, and cross-product workflows
|
|---|
| Not for | - Workspaces whose acceptable-use policy forbids unofficial clients (consider the OAuth hosted tier)
- Compliance-sensitive environments uncomfortable reusing personal browser session credentials
- Teams needing official Slack support (not affiliated with Slack Technologies)
| - Users without an Atlassian Cloud site or relevant product permissions
- Deployments requiring a self-hosted MCP server
- Users unwilling to grant an AI client access to Atlassian data or actions
- Jira Service Management or Bitbucket Cloud workflows requiring OAuth authentication
|
|---|
| Required permissions | - Requires Slack browser session token (xoxc-) and cookie (xoxd-); the agent's footprint equals your browser session exactly
- On macOS, Chrome auto-extraction reads Chrome's local LevelDB and the Chrome Safe Storage key from the Keychain
- Write tools (send, react, mark read) carry MCP destructive annotations so clients can gate them
| - Jira and Confluence provide read, write, and search permission groups
- Jira Service Management provides read and write access through API tokens only
- Bitbucket Cloud provides read and write access through scoped API tokens only
- Compass is available through OAuth 2.1 only
- The first OAuth installer for a site must have access to the Atlassian apps requested by the MCP scopes
- Organization administrators can manage domain controls, API-token authentication, app access, and audit logs
|
|---|
| Risks and side effects | - Automating your own session is a gray area under Slack's terms — this is an unofficial client
- No app install appears in the admin panel, but traffic is still subject to workspace compliance exports, DLP, and retention
- Session tokens expire roughly every 1–2 weeks, requiring re-extraction or the hosted OAuth tier
- Tokens equate to your full Slack session; a leak means a session leak
| - AI clients can perform Jira, Confluence, Jira Service Management, Bitbucket, and Compass actions on the user’s behalf
- Prompt injection, indirect prompt injection, and tool-poisoning attacks may cause data exfiltration or unintended changes
- Use least privilege, scoped tokens, and minimal project or workspace access
- Require human confirmation for high-impact or destructive actions and monitor audit logs
|
|---|
| Supported clients | Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Gemini CLI, Codex | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
|---|
| Tools | 21 | 0 |
|---|