Dart MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_configB | Get information about the user's space, including all of the possible values that can be provided to other endpoints. This includes available assignees, dartboards, folders, statuses, tags, priorities, sizes, and all custom property definitions. |
| create_taskC | Create a new task in Dart. You can specify title, description, status, priority, size, dates, dartboard, assignees, tags, parent task, custom properties, and task relationships. |
| list_tasksC | List tasks from Dart with optional filtering parameters. You can filter by assignee, status, dartboard, priority, due date, and more. |
| get_taskC | Retrieve an existing task by its ID. Returns the task's information including title, description, status, priority, dates, custom properties, and more. |
| update_taskC | Update an existing task. You can modify any of its properties including title, description, status, priority, dates, assignees, tags, custom properties, and task relationships. |
| delete_taskA | Move an existing task to the trash, where it can be recovered if needed. Nothing else about the task will be changed. |
| create_docC | Create a new doc in Dart. You can specify title, text content, and folder. |
| list_docsC | List docs from Dart with optional filtering parameters. You can filter by folder, title, text content, and more. |
| get_docC | Retrieve an existing doc by its ID. Returns the doc's information including title, text content, folder, and more. |
| update_docC | Update an existing doc. You can modify its title, text content, and folder. |
| delete_docA | Move an existing doc to the trash, where it can be recovered if needed. Nothing else about the doc will be changed. |
| add_task_commentA | Add a comment to an existing task without modifying the task description. Comments support markdown formatting. |
| list_task_commentsC | List comments from Dart with optional filtering parameters. You can filter by author, task, text content, dates, and more. |
| get_dartboardB | Retrieve an existing dartboard by its ID. Returns the dartboard's information including title, description, and all tasks within it. |
| get_folderC | Retrieve an existing folder by its ID. Returns the folder's information including title, description, and all docs within it. |
| get_viewB | Retrieve an existing view by its ID. Returns the view's information including title, description, and all tasks within it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| Create task | Create a new task in Dart |
| Create doc | Create a new document in Dart |
| Summarize tasks | Get a summary of tasks with optional filtering |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Every tool has a clearly distinct purpose targeting specific resources and actions, with no overlap. For example, create_task vs. update_task vs. delete_task handle different lifecycle stages, and tools like get_config or add_task_comment serve unique functions that don't conflict with others.
All tools follow a consistent verb_noun pattern (e.g., create_doc, delete_task, get_config), with no deviations in style or convention. The naming is predictable and enhances readability across the entire set.
With 16 tools, the server is well-scoped for managing tasks, docs, folders, dartboards, views, and comments in Dart. Each tool earns its place by covering essential CRUD operations and auxiliary functions like configuration retrieval, without being overly sparse or bloated.
The tool surface provides complete CRUD/lifecycle coverage for the domain, including tasks (create, get, update, delete, list, add comment, list comments), docs (create, get, update, delete, list), and supporting resources like folders, dartboards, views, and config. There are no obvious gaps that would hinder agent workflows.