AFFiNE MCP Server is designed for three common scenarios:

• Run a local stdio MCP server for Claude Code, Codex CLI, Cursor, or Claude Desktop
• Expose a remote HTTP MCP endpoint for hosted or browser-connected clients
• Automate AFFiNE workspace, document, database, organization, and comment workflows through a stable MCP tool surface

Highlights:

• Supports AFFiNE Cloud and self-hosted AFFiNE instances
• Supports stdio and HTTP transports
• Supports token, cookie, and email/password authentication
• Exposes 84 canonical MCP tools backed by AFFiNE GraphQL and WebSocket APIs
• Includes semantic page composition, native template instantiation, database intent composition, capability and fidelity reporting, and workspace blueprint helpers
• Includes Docker images, health probes, and end-to-end test coverage

Scope boundaries:

• This server can access only server-backed AFFiNE workspaces
• Browser-local workspaces stored only in local storage are not available through AFFiNE server APIs
• AFFiNE Cloud requires API-token-based access for MCP usage; programmatic email/password sign-in is blocked by Cloudflare

FAQ

它支持 AFFiNE Cloud 吗？ 答：支持。README 写明支持 AFFiNE Cloud 与自托管；Cloud 场景通常使用 API token 访问。

支持 stdio 和 HTTP 吗？ 答：支持。README 描述了默认 stdio 与 HTTP /mcp 传输。

如何降低风险？ 答：用最小权限限制工具面、token 不入库，先从只读开始再逐步放开。