← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionMCP AtlassianModel Context Protocol server for Confluence and JiraAnytype MCP ServerOfficial MCP server that lets AI assistants manage your encrypted Anytype wiki in natural language.
FMRS56 / 100 · C64 / 100 · C
Reliability7 / 2010 / 20
Security and permissions9 / 2011 / 20
Maintenance14 / 2014 / 20
Documentation14 / 2014 / 20
Setup experience12 / 2015 / 20
Best for
  • Teams that want an AI assistant to read and write Jira issues and Confluence pages directly
  • Organizations running both Atlassian Cloud and Server/Data Center environments
  • Developers who want JQL/CQL search, issue creation, and status transitions inside their IDE or chat client
  • 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
Not for
  • Users without an Atlassian Jira or Confluence account/instance
  • Scenarios requiring official Atlassian support guarantees (this is not an official Atlassian product)
  • Environments that cannot securely store or rotate API tokens/.env files
  • 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
Required permissions
  • URL(s) of the Jira and/or Confluence instance
  • Atlassian account email + API token (Cloud), or a Personal Access Token (Server/Data Center)
  • Whatever read/write permissions that account actually holds in Jira/Confluence (creating/updating issues, creating/updating pages, and adding comments require write access)
  • 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
Risks and side effects
  • A leaked API token or PAT can be used to read and write Jira/Confluence data as that account
  • The README explicitly warns to keep .env files secure to avoid credential exposure
  • Creating, updating, and transitioning issues, and creating/updating pages, are write operations — misconfigured automation could cause unintended data changes
  • Not officially maintained by Atlassian, so updates and security response depend on the community repository maintainers
  • 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
Supported clientsClaude Desktop, Cursor, Autohand CodeClaude Desktop, Cursor, Windsurf, Raycast, Claude Code, LM Studio, Kiro
Tools100