F
licenseNot graded
qualityC
maintenanceMCP server that exposes self-hosted AppFlowy Cloud REST API to AI assistants, enabling management of AppFlowy workspaces and documents through natural language.
-
AFFiNE MCP Server
by irfanhak123
Related Servers
Alternatives to AFFiNE MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server for interacting with Logseq graphs, enabling AI assistants to read, create, and manipulate Logseq content.8MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to access and manage your local Obsidian vault through a standardized protocol.146,347 npm2Apache 2.0
Notion MCP Serverofficial
AlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to interact with the Notion API, allowing them to search, read, comment on, and create content in Notion workspaces through natural language commands.19166,417 npm4,666MIT- AlicenseAqualityAmaintenanceAn unofficial MCP server that enables AI assistants to search, read, create, and update pages in your NotePM workspace.844 npm1MIT
- AlicenseBqualityBmaintenanceA live MCP server that connects AI assistants to a running Obsidian instance, enabling full app automation including reading notes, clicking UI elements, managing plugins, and executing JavaScript.4319 npm3MIT
TDQS
B3.4/5.0
Scored across 96 tools
Disambiguation4/5
Most tools have clearly distinct purposes (workspaces, docs, tags, databases, canvas, comments, collections, folders, properties, icons, user, blobs, notifications), and descriptions explicitly distinguish near-overlaps like get_doc vs read_doc and find_doc_by_title vs search_docs. A few pairs (update_surface_element vs update_edgeless_block) could cause confusion, but their descriptions are clear enough.
Naming Consistency4/5
The overwhelming majority follow a consistent verb_noun snake_case pattern (list_, get_, create_, update_, delete_, append_, etc.). Minor deviations like 'current_user' (a noun phrase rather than verb-first) and a few multi-word descriptive names (analyze_doc_fidelity, instantiate_template_native) break the pattern slightly but do not hinder readability.
Tool Count1/5
At 96 tools, this is an extreme count, far exceeding the 'well-scoped' guideline of 3-15 tools. Even accounting for AFFiNE's broad feature set, the sheer number imposes a high selection burden and increases the risk of misselection, making the tool surface unwieldy.
Completeness4/5
The server covers an impressively broad range of AFFiNE domains with full CRUD or lifecycle operations for workspaces, docs, tags, databases, canvas elements, comments, collections, folders, properties, icons, blobs, and notifications. Minor gaps exist (e.g., no full-text search, no explicit move-doc-to-folder tool, no workspace member management), but the core workflows are well covered.
Maintenance
ActivityStale
ResponsivenessNo issues