| FMRS | 64 / 100 · C | 66 / 100 · C |
|---|
| Reliability | 10 / 20 | 8 / 20 |
|---|
| Security and permissions | 11 / 20 | 15 / 20 |
|---|
| Maintenance | 14 / 20 | 15 / 20 |
|---|
| Documentation | 14 / 20 | 15 / 20 |
|---|
| Setup experience | 15 / 20 | 13 / 20 |
|---|
| Best for | - Users who already rely on Anytype as a personal or collaborative knowledge base
- Users who want to create and manage Anytype objects quickly with natural language
- Advanced users running the Anytype desktop app locally who want AI assistant integration
| - 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 without Anytype installed or running and unable to obtain an API key
- Scenarios needing a remotely hosted service instead of a local stdio process
- Users who want zero configuration without setting environment variables
| - 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 an Anytype API key passed via an Authorization: Bearer header
- Needs access to the local Anytype API service (default http://127.0.0.1:31009)
- Passes authentication headers through the OPENAPI_MCP_HEADERS environment variable, treated as secret
- Runs an npx command locally as a stdio subprocess
| - 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 | - OPENAPI_MCP_HEADERS contains the API key; leaking this configuration can expose Anytype data
- The server can create and modify spaces, objects and lists on behalf of the key owner
- Running npx -y downloads and executes package code from npm
- Pointing ANYTYPE_API_BASE_URL at an untrusted address can send authentication headers there
| - 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 Desktop, Cursor, Windsurf, Raycast, Claude Code, LM Studio, Kiro | 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 |
|---|