workflowy
Related Servers
Alternatives to workflowy
- MIT
- 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.742 PyPI12MIT
- AlicenseCqualityDmaintenanceIntegrates WorkFlowy's outline and task management capabilities with LLM applications, enabling hierarchical node creation, updates, completion tracking, and navigation through WorkFlowy's API.351MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for mind-wiki — access your personal knowledge wiki from any directory or MCP-compatible client.MIT
- FlicenseBqualityNot gradedmaintenanceAn MCP server that exposes Threads CLI data for managing hierarchical threads, containers, and progress logs. It enables users to create, organize, and track task history while maintaining compatibility with the Threads CLI storage.29-
- AlicenseAqualityDmaintenanceUnofficial MCP server to manage grocery lists in OurGroceries. Enables listing, adding, completing, removing, and moving items.6MIT
- AlicenseAqualityBmaintenanceLocal MCP server for plain Markdown notes: list, read, create and search notes, and manage their tasks and Kanban board (move cards, toggle tasks, set start and due dates).9102MIT
- AlicenseBqualityBmaintenanceAn independent, self-hostable MCP server for Trello that lets MCP clients discover boards and workspaces, search, and manage cards, lists, labels, checklists, comments, and attachments. Supports stdio and Streamable HTTP with user-provided Trello API key/token authentication.77384 npm10MIT
- AlicenseAqualityBmaintenanceMCP server for TickTick — create, update, complete, move, and filter tasks (plus subtasks, completed-task retrieval, and recurring reminders) via the TickTick v2 API. Maintained fork of jen6/ticktick-mcp adding field-preserving updates, day-of-week date validation, completion tracking and more.141GPL 3.0
TDQS
Scored across 10 tools
Each tool targets a distinct operation: retrieval (get, list, search), resolution (id), reporting (various report_*), and listing targets. No two tools overlap in function; descriptions clearly differentiate them.
All tools follow a consistent 'workflowy_<verb>_<noun>' pattern with verbs like get, id, list, report_*, search, targets. The report tools share a uniform prefix. No mixing of conventions.
10 tools is a reasonable count for a read-only Workflowy server. It covers querying, searching, reporting, and identifier resolution without being excessive. Could be moderately expanded but is well-scoped.
The tool surface covers reading, searching, and reporting comprehensively, but lacks any write operations (create, update, delete) that are typical for a workflowy integration. This omission creates a notable gap for tasks requiring modification.