Skip to main content
Glama

Dynalist MCP Server

A Model Context Protocol server for Dynalist.io - the infinite document outliner.

Enables Claude and other AI assistants to read, write, and manipulate Dynalist documents programmatically.

Features

Read Operations

  • list_documents - List all documents and folders in your account

  • search_documents - Search documents/folders by name (returns ID, URL, type)

  • read_node_as_markdown - Extract bullet points as Markdown (supports deep links, depth limits, notes)

  • search_in_document - Search content within a document (returns parents + optional children)

  • get_recent_changes - Get nodes created/modified in a time period (with parent context)

Write Operations

  • send_to_inbox - Add items to your Dynalist inbox (supports hierarchical markdown)

  • edit_node - Modify existing nodes (content, note, checkbox, heading, color)

  • insert_node - Insert a single new node

  • insert_nodes_from_markdown - Bulk import from indented markdown/bullet lists

Structure Operations

  • delete_node - Remove a node (optionally with all children)

  • move_node - Move node with explicit parent/index

  • move_node_relative - Move node + subtree relative to another node (after/before/as_child)

Related MCP server: WorkFlowy MCP Server

Setup

1. Get your Dynalist API Token

Visit https://dynalist.io/developer and generate an API token.

2. Install dependencies

npm install
npm run build

3. Configure Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "dynalist": {
      "command": "node",
      "args": ["/FULL/PATH/TO/dynalist-mcp/dist/index.js"],
      "env": {
        "DYNALIST_API_TOKEN": "your_token_here"
      }
    }
  }
}

Usage Examples

read_node_as_markdown with url: "https://dynalist.io/d/abc123#z=xyz789"

Returns Markdown preserving hierarchy:

- Parent item
    - Child item
        - Grandchild with checkbox [x]
    - Another child

Bulk insert from markdown

insert_nodes_from_markdown with:
  file_id: "abc123"
  parent_node_id: "xyz789"
  markdown: "- Item 1\n    - Sub-item\n- Item 2"

Search in document

search_in_document with:
  file_id: "abc123"
  query: "meeting notes"

Add to inbox

send_to_inbox with content: "Remember to review the PR"

Development

npm run build      # Compile TypeScript
npm run dev        # Watch mode
npm run inspector  # Test with MCP Inspector

Testing with MCP Inspector

DYNALIST_API_TOKEN=your_token npx @modelcontextprotocol/inspector node dist/index.js

License

MIT

Available Tools

12 tools
delete_nodeA

Delete a node from a Dynalist document. By default, only the node is deleted and its children move up to the parent. Use include_children=true to delete the node AND all its descendants.

Inputs: node_id (required), url, file_id, include_children.

edit_nodeC

Edit an existing node in a Dynalist document

Inputs: node_id (required), url, file_id, content, +5 more.

get_recent_changesA

Get nodes created or modified within a time period. WARNING: Long time periods with active documents can return many words.

Inputs: since (required), url, file_id, until, +4 more.

insert_nodeC

Insert a new node into a Dynalist document

Inputs: parent_id (required), content (required), url, file_id, +4 more.

insert_nodes_from_markdownC

Insert multiple nodes from indented markdown/text. Supports both '- bullet' format and plain indented text. Preserves hierarchy.

Inputs: url (required), content (required), position.

list_documentsB

List all documents and folders in your Dynalist account

Inputs: no named parameters.

move_nodeC

Move a node to a different location in a Dynalist document

Inputs: node_id (required), parent_id (required), url, file_id, +1 more.

move_node_relativeA

Move a node (and all its children) to a new position relative to a reference node. This is the intuitive way to reorganize your outline - just specify where you want the node to go.

Inputs: source_url (required), reference_url (required), position (required).

read_node_as_markdownA

Read a Dynalist document or specific node and return it as Markdown. Provide either a URL (with optional #z=nodeId deep link) or file_id + node_id. WARNING: Large documents may return many words - use max_depth to limit.

Inputs: url, file_id, node_id, max_depth, +3 more.

search_documentsB

Search for documents and folders by name. Returns matching items with their ID, title, URL, and type.

Inputs: query (required), type.

search_in_documentB

Search for text in a Dynalist document. Returns matching nodes with optional parent context and children. WARNING: Many matches with parents/children can return many words.

Inputs: query (required), url, file_id, search_notes, +3 more.

send_to_inboxC

Send items to your Dynalist inbox. Supports indented markdown/bullets for hierarchical content.

Inputs: content (required), note, checkbox.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific Dynalist operations, such as node manipulation (delete, edit, insert, move), document management (list, search), and content handling (read as markdown, send to inbox). No tools overlap in functionality, making it easy for an agent to select the correct one based on the task.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, such as delete_node, edit_node, list_documents, and search_documents. This uniformity makes the tool set predictable and easy to understand, enhancing usability for agents.

    Tool Count5/5

    With 12 tools, the server is well-scoped for managing Dynalist documents and nodes, covering core operations like CRUD for nodes, document listing and searching, and content import/export. Each tool serves a specific, necessary function without redundancy or bloat.

    Completeness5/5

    The tool set provides complete coverage for the Dynalist domain, including full CRUD/lifecycle operations for nodes (create, read, update, delete, move), document management (list, search), and advanced features like markdown conversion and inbox integration. No obvious gaps exist that would hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers