MCP Todo.txt Integration
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TODO_FILE_PATH | No | The path to the Todo.txt file. If not set, the default path is `todo.txt` in the project root. | todo.txt |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add-taskB | Add a new task to the todo list. Description must be plain text. Priority must be a single uppercase letter (A-Z). Contexts must start with @, projects with +. |
| complete-taskB | Mark a task as completed by its 1-based ID. |
| delete-taskB | Delete a task by its 1-based ID. |
| list-tasksC | List all tasks, optionally filtered by priority, context, project, or metadata. |
| search-tasksB | Search for tasks containing a query string. |
| sort-tasksC | Sort tasks by priority, creation date, or completion date. |
| filter-tasksC | Filter tasks by specific criteria (priority, context, project). |
| add-metadataB | Add custom metadata (key-value pairs) to a task by ID. |
| remove-metadataC | Remove specific metadata keys from a task by ID. |
| batch-operationsB | Perform batch operations (update, delete, mark-complete) on tasks matching criteria. |
| update-taskC | Update a task's fields (description, priority, contexts, projects, metadata) by ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| suggest-context-tasks | |
| suggest-project-tasks |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tasks |
TDQS
Scored across 11 tools
Most tools have clear, distinct purposes (add, update, delete, complete, list, search, sort, filter, metadata operations). However, filter-tasks and list-tasks overlap somewhat since list-tasks already supports filtering by priority, context, project, or metadata, which could cause an agent to pick the wrong one.
Tool names consistently use a verb-noun pattern (add-task, update-task, delete-task, list-tasks, search-tasks, sort-tasks, complete-task). Minor deviations: batch-operations is a noun phrase rather than verb-noun, and filter-tasks overlaps with list-tasks' filtering capability.
11 tools is a reasonable count for a todo.txt server covering task CRUD, metadata, search, sorting, filtering, and batch operations. It is slightly on the higher side but each tool addresses a distinct operation, so the count feels appropriate.
The tool set covers the core todo.txt lifecycle well: add, list, update, complete, delete, search, sort, filter, and metadata management. Minor gaps include no explicit undo/reopen-completed-task operation and no way to move tasks between lists, but these are not critical for a todo.txt integration.