Todokit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TODOKIT_TODO_FILE | No | Path to the todos.json file. Can be absolute or relative. By default, todos are stored in todos.json next to the server package. |
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 |
|---|---|
| add_todoB | Add a new todo item |
| add_todosB | Add multiple todo items in one call |
| list_todosB | List todos with filtering, search, sorting, and pagination |
| update_todoB | Update fields on a todo item (supports search and tag ops) |
| complete_todoB | Set completion status for a todo item |
| delete_todoA | Delete a todo item (supports dry-run) |
| delete_todosA | Delete multiple todos matching filters (requires at least one filter, defaults to limit=10 for safety) |
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 7 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools cover specific operations like adding single/multiple items, completing, deleting single/multiple items, listing, and updating, each with unique scopes that don't overlap.
All tool names follow a consistent verb_noun pattern (e.g., add_todo, complete_todo, delete_todo) with clear and predictable naming conventions throughout the set.
With 7 tools, the count is well-scoped for a todo management server. Each tool earns its place by covering essential CRUD operations and bulk actions without being excessive or sparse.
The tool set provides complete CRUD/lifecycle coverage for the todo domain, including creation (add_todo, add_todos), reading (list_todos), updating (update_todo, complete_todo), and deletion (delete_todo, delete_todos), with no obvious gaps.