F
licenseA
qualityD
maintenanceProvides LLM access to Workflowy's API, enabling agents to create, read, update, delete, and reorganize nodes in a Workflowy outline.
12
-
WorkFlowy MCP Server
by daniel347x
Related Servers
Alternatives to WorkFlowy MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables interaction with WorkFlowy's outline and task management system through 8 comprehensive tools. Supports creating, updating, searching, and managing hierarchical nodes and tasks with high-performance async operations.711MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to interact with Workflowy through the Model Context Protocol, supporting operations like creating, updating, deleting, and listing nodes.MIT
- AlicenseNot gradedqualityBmaintenanceLets humans, scripts, and AI agents safely read, search, organize, and edit a WorkFlowy account.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Todoist tasks and projects with CRUD operations, hierarchical navigation, and completed task retrieval.5 npmMIT
- FlicenseAqualityDmaintenanceEnables Claude and other AI assistants to read, write, and manipulate Dynalist.io documents programmatically, including operations like searching, editing nodes, bulk importing from markdown, and managing document structure.122-
TDQS
C2.4/5.0
Scored across 35 tools
Disambiguation2/5
There is significant overlap and confusion among tools, especially between deprecated and current versions (e.g., workflowy_create_single_node vs. workflowy_etch), and between similar NEXUS tools (e.g., nexus_glimpse, nexus_scry, workflowy_glimpse, workflowy_scry). The NEXUS tools have cryptic, overlapping purposes (e.g., nexus_anchor_gems, nexus_anchor_jewels) that are hard to distinguish, leading to high misselection risk.
Naming Consistency3/5
Naming is mixed with some consistency: most WorkFlowy tools follow a workflowy_verb_noun pattern, and NEXUS tools use nexus_verb_noun, but there are deviations like generate_markdown_from_json and deprecated tools with __WARNING__ suffixes. The patterns are readable but not fully uniform across the set.
Tool Count2/5
With 35 tools, the count is excessive for a WorkFlowy server, especially given many deprecated and overlapping tools. This bloats the interface and makes it hard for agents to navigate efficiently, indicating poor scoping and unnecessary complexity.
Completeness4/5
The tool set covers core WorkFlowy operations (CRUD, move, complete) and advanced NEXUS features (exploration, transformation, weaving), with minor gaps like bulk updates. However, the domain is well-covered despite some redundancy, allowing agents to perform most tasks.
Maintenance
ActivityInactive
ResponsivenessNo issues