Coding Todo MCP Server

Manage a coding project's todo list with this MCP server. Exposed over MCP by the coding todo mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

This MCP server provides tools and resources for managing a coding project's todo list.

Its toolset

Everything the assistant can do here goes through one of these:

• add_todo — Adds a new todo item to the list
• Arguments — - title: Title of the todo item (required)
• description — Detailed description of the todo item (required)
• project — Project name (optional)
• priority — Priority from 1 (lowest) to 5 (highest) (optional, default: 1)
• tags — List of tags related to the todo (optional)
• update_todo_status — Updates the status of an existing todo item
• status — New status (pending/in_progress/completed) (required)
• delete_todo — Deletes a todo item from the list
• update_todo — Updates the details of an existing todo item
• title — New title (optional)

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Coding Todo's toolset — add_todo, Arguments, description and 8 more — is a fair guide to whether it matches your workflow. It is maintained by dennismartis; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Coding Todo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Coding Todo.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the coding todo mcp server does with a few real requests.