add_todo
Agregar una nueva tarea a la lista
LABSCO SUMMARY
Four tools, no ambition, and the repository is named after the architecture rather than the product — read it as a reference implementation.
This is the smallest complete surface a task list can have, which makes it a reasonable thing to read if you are working out how to structure an MCP server. As a task manager it competes with tools that have projects, labels, due dates and recurrence, and it is not trying to. Take it as a worked example of clean architecture applied to MCP, and judge it on the code rather than the feature list. Tool descriptions are in Spanish.
What it is
A minimal todo server: the four operations a task list needs, implemented as a clean-architecture demonstration.
What you get
- add_todo, list_todos with status, complete_todo and delete_todo — the complete set for a task list and no more.
Requirements
Nothing to supply.
Setup effort
One command — npx -y mcp-todo-server
USE CASES
01
Keeping a simple list
Add tasks, see them with their status, tick them off and remove what is done.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
complete_todo
Marcar una tarea como completada
delete_todo
Eliminar una tarea de la lista
list_todos
Listar todas las tareas con su estado
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-todo-server": {
"command": "npx",
"args": [
"-y",
"mcp-todo-server"
]
}
}
}npx
TERMINAL
npx -y mcp-todo-server
