How do I use To Do List MCP?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@To Do List MCP add buy groceries and call mom to my to-do list" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

To Do List MCP

by Wesley-Blake

Overview Schema Source Related Servers Discussions Admin

Python

Local

To Do List MCP

A minimal Model Context Protocol server that exposes a personal to-do list backed by SQLite. Built with the official Python mcp SDK.

Tools

Tool	Description	Arguments
`task_add`	Add a task, or a list of tasks in one call	`task_name: str \| list[str]`
`task_get`	List all incomplete tasks	—
`task_update`	Rename a task and/or set its status	`task_id: int`, `task_name: str`, `task_status: bool = False`
`task_complete`	Mark a task complete	`task_id: int`

Tasks are stored in todolist.db (SQLite), created automatically on first run in the server's working directory.

Related MCP server: TodoSQLite MCP Server

Requirements

Python >= 3.13
uv

Installation

Clone the repo and install dependencies with uv:

uv sync

Usage

Claude Desktop

Add the server to your claude_desktop_config.json (Claude menu → Settings → Developer → Edit Config), or install it automatically with the MCP CLI:

uv run mcp install src/to_do_list_mcp/server.py --name "To Do List"

This adds an entry like the following:

{
  "mcpServers": {
    "To Do List": {
      "command": "uv",
      "args": [
        "run",
        "--with",
        "mcp[cli]",
        "mcp",
        "run",
        "/absolute/path/to/to_do_list_mcp/src/to_do_list_mcp/server.py"
      ]
    }
  }
}

Restart Claude Desktop afterwards for the server to be picked up.

Development

Run the server directly with the MCP Inspector for interactive testing:

uv run mcp dev src/to_do_list_mcp/server.py

License

No license specified.

Available Tools

4 tools

task_addD

ParametersJSON Schema

Name	Required	Description	Default
`task_name`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

task_completeD

ParametersJSON Schema

Name	Required	Description	Default
`task_id`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

task_getD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

task_updateD

ParametersJSON Schema

Name	Required	Description	Default
`task_id`	Yes
`task_name`	Yes
`task_status`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

4 tool updatesv0.1.0Sep 13, 2026
- First observedtask_add
- First observedtask_complete
- First observedtask_get
- First observedtask_update

Deploy Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.9/5.0

Scored 2026-09-13 01:40 across 4 tools

Disambiguation4/5

task_add, task_update, task_complete, and task_get target reasonably distinct actions on a task. However, task_complete overlaps with task_update (completing is a specialized update), and the absence of descriptions leaves boundaries somewhat implicit.

Naming Consistency5/5

All four tools follow a strict task_<verb> snake_case pattern with no deviations. The convention is predictable and immediately readable.

Tool Count4/5

Four tools is a sensible, well-scoped surface for a simple to-do list server. It is on the lean side but each tool maps to a clear operation.

Completeness3/5

The set covers create, read, update, and complete, but lacks a list/query-all operation and a delete/remove operation. These are notable gaps for a to-do domain that will force agents to work around missing lifecycle steps.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

Done Bear A
com.donebear
Local-first task manager: create, edit, and complete tasks, projects, and checklists via MCP.
Project Management App Automation
151
tideeOAuth
com.tidee
Add items to your tidee workspace from ordinary language, read what is there, and mark things done.
Project Management Workplace & Productivity
1
Todo MCP A
io.github.AnkitPat
Create, list, and complete todo items through MCP.
Project Management Workplace & Productivity
1
CalmLoop Task Manager
in.calmloop
Manage tasks, Focus Zone, notes, projects, and task history from compatible AI assistants.
Project Management Note Taking
1

Related MCP Servers

Tasks MCP Server
App Automation Note Taking Workplace & Productivity
chipocrudos
F
license
B
quality
D
maintenance
Enables task management through natural language commands in English or Spanish. Supports creating, listing, updating, completing, and deleting tasks with local SQLite storage.
Updated a year ago (2025-10-27 23:55 UTC)
7
-
TodoSQLite MCP Server
Project Management Developer Tools
linhnv4dev
F
license
Not graded
quality
D
maintenance
Enables users to manage a personal todo list with CRUD operations, keyword search, and local SQLite storage. Designed for AI agent productivity tools.
Updated 6 months ago (2026-02-28 15:39 UTC)
-
Task Manager MCP Server
Project Management Databases
santiagoarangoEverglow
F
license
Not graded
quality
C
maintenance
Enables CRUD operations on a SQLite task database with filtering by status and priority.
Updated 2 months ago (2026-07-17 08:47 UTC)
-
Intern Task Tracker MCP Server
Project Management Databases
iamsoham25
F
license
Not graded
quality
B
maintenance
Enables managing daily work logs with tools for adding, listing, updating status, deleting, and summarizing tasks, using SQLite for persistent storage.
Updated a month ago (2026-08-12 07:13 UTC)
-