MCP Todo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_STDIO | No | Enable stdio transport for MCP client integration | 1 |
| TODO_MCP_TOKEN | No | Bearer token for HTTP authentication (optional) |
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_todosB | Return all todos in a structured format. |
| add_todoC | Add a todo item |
| toggle_todoC | Toggle a todo by id |
| remove_todoC | Remove a todo by id |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| todos | Current todo list |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: add_todo creates items, list_todos retrieves them, remove_todo deletes by ID, and toggle_todo updates completion status. The actions (add, list, remove, toggle) and targets (todos) are unambiguous, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun pattern with snake_case naming: add_todo, list_todos, remove_todo, toggle_todo. The verbs are descriptive and aligned with CRUD operations, and the noun 'todo' is used consistently across all tools, providing a predictable and readable naming convention.
With 4 tools, this server is well-scoped for a todo management domain. Each tool serves a distinct and essential function (create, read, update, delete), and there are no extraneous or missing tools. The count is appropriate for the simple but complete coverage of todo operations.
The tool set provides complete CRUD/lifecycle coverage for todo management: add_todo for creation, list_todos for retrieval, remove_todo for deletion, and toggle_todo for updating completion status. There are no obvious gaps, and agents can perform all core operations without dead ends.