Workflowy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKFLOWY_API_KEY | Yes | Your Workflowy API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workflowy_create_nodeB | Create a new node (bullet point) in Workflowy. Can specify parent node, content, notes, and display mode. |
| workflowy_get_nodeB | Retrieve details about a specific node by its ID. |
| workflowy_list_nodesA | List child nodes under a parent node. If no parentId is provided, lists root-level nodes. |
| workflowy_searchA | Search for nodes by text content across your ENTIRE Workflowy outline (all nodes including deeply nested children). Returns matching nodes with their IDs and parent relationships. Use this to find nodes anywhere in your hierarchy. |
| workflowy_get_node_hierarchyA | Get a node with its children and descendants to see the full context and structure around it. Useful after finding a node via search to understand where it lives in your outline. |
| workflowy_update_nodeB | Update an existing node's content, notes, priority, or layout mode. |
| workflowy_delete_nodeA | Permanently delete a node and all its children. |
| workflowy_move_nodeB | Move a node to a different location in the hierarchy by changing its parent. |
| workflowy_complete_nodeB | Mark a node as complete (for todo-style nodes). |
| workflowy_uncomplete_nodeC | Mark a node as incomplete (for todo-style nodes). |
| workflowy_exportA | Export your entire Workflowy outline structure. Limited to 1 request per minute. |
| workflowy_list_targetsA | List available shortcuts and system locations in Workflowy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: create, delete, get, update, move, complete/uncomplete, search, list, hierarchy, export, and list targets. Descriptions clarify boundaries, including the difference between get_node (single node by ID), get_node_hierarchy (node with descendants), and list_nodes (children of a parent).
All tools follow the pattern 'workflowy_verb_noun' (e.g., workflowy_create_node, workflowy_get_node_hierarchy). Even 'workflowy_export' and 'workflowy_search' adhere to the verb-only format, maintaining consistency. The prefix ensures clear server ownership.
12 tools is well-scoped for a Workflowy integration. It covers all major CRUD operations, plus domain-specific actions like complete/uncomplete, move, search, and export. The count is neither overwhelming nor too sparse for the domain's complexity.
The tool set covers core node management (CRUD, move, complete/uncomplete, search, export, targets) comprehensively. A minor gap is the lack of explicit sibling reordering, but the move tool can change parent, and hierarchy navigation is supported. Overall, agents have the essential operations to manage outlines effectively.