Claude Todo 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 |
|---|---|
| TodoReadA | Read the current task list. Returns a list of todos with their current state. |
| TodoWriteB | Update the entire task list (complete replacement). Parameters: todos: List of todo items, each containing: - id: Unique identifier for the task - content: Task description - status: Current status (pending, in_progress, completed) - priority: Task priority (high, medium, low) - metadata: Optional additional data Returns success status and count of todos written. |
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 2 tools
The two tools have clearly distinct purposes: TodoRead is for retrieving the task list, while TodoWrite is for replacing it entirely. There is no overlap or ambiguity between these operations.
Both tools follow a consistent TodoVerb naming pattern (TodoRead and TodoWrite), using the same prefix and clear action verbs. This makes their functions immediately understandable and predictable.
With only two tools, the server is severely limited for a todo management domain. It lacks essential operations like creating, updating, or deleting individual tasks, making it impractical for typical todo workflows.
The tool surface is severely incomplete. It only supports reading and full replacement of the task list, missing critical CRUD operations such as add_todo, update_todo, delete_todo, or mark_complete. This will cause frequent agent failures in managing tasks.