Skip to main content
Glama
Workflowy MCP Server

Workflowy MCP Server

by dp-pcs

Workflowy MCP Server

A Model Context Protocol (MCP) server that provides LLM access to Workflowy's API, enabling agents to interact with your Workflowy workspace programmatically.

Features

This MCP server provides tools for:

  • Creating nodes: Add new bullet points to your Workflowy outline

  • Reading nodes: Retrieve node details and list children

  • Updating nodes: Modify existing node content and properties

  • Deleting nodes: Remove nodes from your outline

  • Moving nodes: Reorganize your hierarchy

  • Completing tasks: Mark nodes as complete/incomplete

  • Exporting: Download your entire outline structure

Related MCP server: WorkFlowy MCP Server

Installation

For MCP Hive (BrainTrust Platform)

This server is designed to be onboarded directly to MCP Hive. The platform handles all setup automatically.

Manual Installation

  1. Clone the repository:

git clone https://github.com/yourusername/workflowy-mcp-server.git
cd workflowy-mcp-server
  1. Install dependencies:

npm install
  1. Build the project:

npm run build
  1. Set up environment variables:

export WORKFLOWY_API_KEY="your-api-key-here"
  1. Run the server:

npm start

Configuration

The server requires the following environment variable:

  • WORKFLOWY_API_KEY: Your Workflowy API key (get it from the Workflowy API settings)

Available Tools

workflowy_create_node

Create a new node in your Workflowy outline.

workflowy_get_node

Retrieve details about a specific node.

workflowy_list_nodes

List child nodes under a parent node.

workflowy_update_node

Modify an existing node's content or properties.

workflowy_delete_node

Delete a node from your outline.

workflowy_move_node

Move a node to a different location in the hierarchy.

workflowy_complete_node

Mark a node as complete.

workflowy_uncomplete_node

Mark a node as incomplete.

workflowy_export

Export your entire Workflowy outline.

workflowy_list_targets

List available shortcuts and system locations.

API Reference

This server implements the Workflowy API v1.

License

MIT

Available Tools

12 tools
workflowy_complete_nodeB

Mark a node as complete (for todo-style nodes).

Inputs: nodeId (required).

workflowy_create_nodeB

Create a new node (bullet point) in Workflowy. Can specify parent node, content, notes, and display mode.

Inputs: name (required), parentId, note, priority, +1 more.

workflowy_delete_nodeA

Permanently delete a node and all its children.

Inputs: nodeId (required).

workflowy_exportA

Export your entire Workflowy outline structure. Limited to 1 request per minute.

Inputs: no named parameters.

workflowy_get_nodeB

Retrieve details about a specific node by its ID.

Inputs: nodeId (required).

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.

Inputs: nodeId (required), depth.

workflowy_list_nodesA

List child nodes under a parent node. If no parentId is provided, lists root-level nodes.

Inputs: parentId.

workflowy_list_targetsA

List available shortcuts and system locations in Workflowy.

Inputs: no named parameters.

workflowy_move_nodeB

Move a node to a different location in the hierarchy by changing its parent.

Inputs: nodeId (required), parentId (required), priority.

workflowy_uncomplete_nodeC

Mark a node as incomplete (for todo-style nodes).

Inputs: nodeId (required).

workflowy_update_nodeB

Update an existing node's content, notes, priority, or layout mode.

Inputs: nodeId (required), name, note, priority, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation5/5

    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).

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers