Dynalist MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DYNALIST_API_TOKEN | Yes | Your Dynalist API token (generate at https://dynalist.io/developer) |
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 |
|---|---|
| list_documentsB | List all documents and folders in your Dynalist account |
| search_documentsB | Search for documents and folders by name. Returns matching items with their ID, title, URL, and type. |
| 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. |
| send_to_inboxC | Send items to your Dynalist inbox. Supports indented markdown/bullets for hierarchical content. |
| edit_nodeC | Edit an existing node in a Dynalist document |
| insert_nodeC | Insert a new node into a Dynalist document |
| 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. |
| get_recent_changesA | Get nodes created or modified within a time period. WARNING: Long time periods with active documents can return many words. |
| 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. |
| move_nodeC | Move a node to a different location in a Dynalist document |
| 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. |
| insert_nodes_from_markdownC | Insert multiple nodes from indented markdown/text. Supports both '- bullet' format and plain indented text. Preserves hierarchy. |
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
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.
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.
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.
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.