| FMRS | 54 / 100 · D | 66 / 100 · C | 58 / 100 · C |
|---|
| Reliability | 9 / 20 | 8 / 20 | 13 / 20 |
|---|
| Security and permissions | 11 / 20 | 15 / 20 | 11 / 20 |
|---|
| Maintenance | 9 / 20 | 15 / 20 | 10 / 20 |
|---|
| Documentation | 12 / 20 | 15 / 20 | 13 / 20 |
|---|
| Setup experience | 13 / 20 | 13 / 20 | 11 / 20 |
|---|
| Best for | - Users who need AI agents to access Notion workspaces
- MCP workflows involving common page editing and data source operations
- Notion API workflows that benefit from compact responses and simplified tools
| - 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
| - Internal collaboration workflows that need channel history or team notifications
- Development teams testing message automation in a non-production workspace
|
|---|
| Not for | - Workflows that do not use Notion
- Users who need to access content that has not been shared with the integration
- Cases requiring advanced API shapes not covered by the simplified tools when raw JSON tools are unsuitable
| - 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
| - Organizations that prohibit model access to internal chat history
- Workspaces that cannot tightly restrict bot channels and OAuth scopes
|
|---|
| Required permissions | - Read content is required for search, page reads, data source retrieval, and queries
- Insert content is required for creating pages or items and appending blocks
- Update content is required for updating pages, blocks, and data source schemas
- Read comments and Insert comments are required only for comment tools
- User information is required only for user lookup tools
- The integration can access only pages and databases shared with it
| - 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
| - A Slack Bot Token and Team ID
- Least-privilege OAuth scopes for channel history, messages, or reactions
|
|---|
| Risks and side effects | - With insert or update capabilities enabled, an agent can create or modify authorized Notion content
- Overly broad access grants may expose unnecessary pages or databases to the server
- Relevant operations may fail when required Notion capabilities or content access are missing
- The server targets Notion API 2026-03-11 and the current data source model
| - 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
| - Channel history may contain internal or personally sensitive information
- Messages and reactions are visible to real members; confirm channel and content before writes
|
|---|
| Supported clients | Claude Desktop, Cursor | OpenAI ChatGPT, Claude, Cursor, Visual Studio Code (GitHub Copilot), GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote | Claude Desktop, Cursor, Cline |
|---|
| Tools | 9 | 0 | 4 |
|---|