The WorkFlowy MCP Server integrates WorkFlowy's outline and task management with LLM applications through CRUD operations on nodes.
Capabilities:
Create nodes: Add new items with customizable name, notes, layout mode (bullets, todo, h1-h3), position (top/bottom), initial completion status, and parent hierarchy
Update nodes: Modify existing node properties including name, notes, layout mode, and completion status
Retrieve nodes: Fetch specific nodes by ID with all metadata (timestamps, completion status, layout)
List nodes: Navigate the hierarchy by listing root-level nodes or children of any parent node
Delete nodes: Remove nodes and all their children from the outline
Manage completion: Mark nodes as completed or uncompleted for task tracking workflows
Error handling: Receive consistent error responses with type, message, and context
Performance configuration: Optional rate limiting, retry logic, and timeout settings via environment variables
Important Limitations:
No search functionality: Cannot search by name or content; must navigate hierarchically from root
Hierarchical navigation only: Must traverse the tree level-by-level to reach deeply nested nodes
API ID incompatibility: Web interface node IDs are NOT compatible with API IDs
Limited discovery: Requires multiple list operations starting from root to find specific nodes
Provides comprehensive WorkFlowy integration with 8 MCP tools for complete outline and task management, including creating, updating, deleting, and searching nodes, as well as managing task completion status and priorities.
WorkFlowy MCP Server
A Model Context Protocol (MCP) server that integrates WorkFlowy's outline and task management capabilities with LLM applications.
MCP Tools Available
Tool | Description |
| Create new nodes with name, notes, and layout mode |
| Update existing node properties |
| Retrieve a specific node by ID |
| List child nodes of a specific parent |
| Delete a node and its children |
| Mark a node as completed |
| Mark a node as uncompleted |
⚠️ Important Limitations
The WorkFlowy API has significant discovery limitations:
✅ CAN list root-level nodes (call
list_nodeswithout parent_id)✅ CAN navigate down the tree by listing children of discovered nodes
❌ CANNOT search for nodes by name or content
❌ CANNOT jump directly to deeply nested nodes
❌ CANNOT use node IDs from WorkFlowy web URLs (they use different IDs)
Practical Impact:
You must navigate hierarchically from root to find existing nodes
No text search means manually traversing the tree to find specific content
Deep nodes require multiple list operations to reach
The web interface IDs (
workflowy.com/#/abc123) are NOT compatible with API IDs
Quick Start
Prerequisites
Python 3.10 or higher
WorkFlowy account with API access
Claude Desktop or other (local, since it's a python package) MCP-compatible client
Installation
Option 1: Install from PyPI (Recommended)
Option 2: Quick Setup Script
Option 3: Manual Installation from Source
Configuration
Get your WorkFlowy API key:
From WorkFlowy
Configure client: Edit your client configuration (Claude Desktop example):
Mac:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add to the
mcpServerssection:{ "mcpServers": { "workflowy": { "command": "python3", "args": ["-m", "workflowy_mcp"], "env": { "WORKFLOWY_API_KEY": "your_actual_api_key_here", // Optional settings (uncomment to override defaults): // "WORKFLOWY_API_URL": "https://workflowy.com/api/v1", // "WORKFLOWY_REQUEST_TIMEOUT": "30", // "WORKFLOWY_MAX_RETRIES": "3", // "WORKFLOWY_RATE_LIMIT_REQUESTS": "60", // "WORKFLOWY_RATE_LIMIT_WINDOW": "60" } } } }Restart your client to load the MCP server
Usage
Once configured, you can use WorkFlowy tools with your agent:
Working with New Nodes
Navigating Existing Nodes
Since there's no search, you must navigate from root:
Note: The node IDs from the web interface URLs are NOT compatible with the API.
Development
Setup Development Environment
Project Structure
Running Tests
API Reference
Node Structure
Error Handling
All tools return a consistent error format:
Performance
Automatic rate limiting prevents API throttling
Token bucket algorithm for smooth request distribution
Adaptive rate limiting based on API responses
Connection pooling for efficient HTTP requests
Contributing
See CONTRIBUTING.md for development setup and contribution guidelines.
License
MIT License - see LICENSE file for details.
Support
Acknowledgments
Built with FastMCP framework
Integrates with WorkFlowy API
Compatible with Claude Desktop and other MCP clients