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 (required) | |
| WORKFLOWY_MAX_RETRIES | No | Maximum number of retries for failed requests | 3 |
| WORKFLOWY_API_BASE_URL | No | WorkFlowy API base URL | https://beta.workflowy.com/api |
| WORKFLOWY_REQUEST_TIMEOUT | No | Request timeout in seconds | 30 |
| WORKFLOWY_RATE_LIMIT_WINDOW | No | Rate limit window in seconds | 60 |
| WORKFLOWY_RATE_LIMIT_REQUESTS | No | Maximum number of requests per rate limit window | 60 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workflowy_create_nodeC | Create a new node in WorkFlowy |
| workflowy_update_nodeC | Update an existing WorkFlowy node |
| workflowy_get_nodeB | Retrieve a specific WorkFlowy node by ID |
| workflowy_list_nodesB | List WorkFlowy nodes (omit parent_id for root) |
| workflowy_delete_nodeA | Delete a WorkFlowy node and all its children |
| workflowy_complete_nodeB | Mark a WorkFlowy node as completed |
| workflowy_uncomplete_nodeB | Mark a WorkFlowy node as not completed |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| workflowy_outline | The complete WorkFlowy outline structure |
TDQS
Scored across 7 tools
Every tool has a clearly distinct purpose targeting specific CRUD operations on WorkFlowy nodes, with no ambiguity between them. The action verbs (complete, create, delete, get, list, uncomplete, update) are mutually exclusive and well-defined for the node management domain.
All tools follow a perfect verb_noun pattern with consistent 'workflowy_' prefix and snake_case throughout. The naming convention is completely predictable, making it easy for agents to understand and use the tool set.
Seven tools is an ideal number for this node management server, providing complete CRUD coverage plus completion status management. Each tool earns its place with no redundancy, and the count is well-scoped for the domain without being overwhelming.
The tool set provides complete lifecycle coverage for WorkFlowy nodes with create, read (get/list), update, delete, plus completion status management (complete/uncomplete). There are no obvious gaps in the surface for node operations, enabling full agent workflows.