Todolist MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TODOLIST_MCP_DB_PATH | No | Path to SQLite database | ~/.todolist-mcp/todolist.db |
| TODOLIST_MCP_TOKEN_PATH | No | Path to token file | ~/.todolist-mcp/token.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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_taskB | Create a new task. |
| get_taskB | Get a task by ID. |
| list_tasksC | List tasks with optional filters. |
| update_taskC | Update a task. |
| delete_taskC | Delete a task. |
| complete_taskA | Mark a task as completed. |
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 6 tools
Each tool targets a distinct task operation: create, get, list, update, delete, and complete. No overlap or ambiguity between them.
All tool names follow the consistent verb_noun pattern using snake_case: create_task, get_task, list_tasks, update_task, delete_task, complete_task.
Six tools is a well-scoped set for a task management server, covering the essential lifecycle without unnecessary bloat.
The tool set covers full CRUD operations plus a completion action, providing complete lifecycle coverage for tasks. No obvious gaps.