| FMRS | 47 / 100 · D | 66 / 100 · C |
| Reliability | 5 / 20 | 8 / 20 |
|---|
| Security and permissions | 9 / 20 | 15 / 20 |
|---|
| Maintenance | 9 / 20 | 15 / 20 |
|---|
| Documentation | 12 / 20 | 15 / 20 |
|---|
| Setup experience | 12 / 20 | 13 / 20 |
| Best for | - Users who want Notion, Monday, Airtable, Jira, Slack, and similar tools inside MCP hosts like Claude, Cursor, Cline, or WindSurf
- No-code users who prefer not to install and maintain a local server
- Teams wanting a single hub for multiple productivity integrations
| - 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 | - Users who need a local stdio server (the local version is deprecated)
- Apps not among the supported providers and not covered by an integration request
- Security-sensitive environments unwilling to delegate credentials to a third-party cloud hub
| - 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 | - OAuth2-style account access authorization to supported apps such as Notion, Monday, Airtable, Jira, Slack, Google Drive, Office 365, Miro, Intercom, and PayPal
| - 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 | - Credentials and data pass through the WayStation cloud service, a third-party hosted platform
- OAuth2 scopes per app may be broad; connect with least privilege
- Granting cloud access to work accounts requires evaluating compliance and data residency requirements
| - 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, Cursor, Cline, Windsurf | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
| Tools | 0 | 0 |