Todo Markdown▌

by danjdewhurst
Manage your tasks efficiently with Todo Markdown—CRUD todo lists stored in markdown files, featuring UUID tracking and c
Provides todo list management with markdown file storage, offering CRUD operations for listing, adding, updating, and deleting tasks with persistent UUID tracking and human-readable checkbox format.
best for
- / Developers who prefer markdown-based task management
- / AI assistants managing user todo lists
- / Teams using markdown workflows for project tracking
capabilities
- / List all todo items from markdown file
- / Add new todo items with descriptions
- / Update existing todo item status and text
- / Delete specific todo items by ID
- / Clear all completed tasks at once
what it does
Manages todo lists stored in markdown files with standard checkbox format. Tracks each item with persistent UUIDs while maintaining human-readable format.
about
Todo Markdown is a community-built MCP server published by danjdewhurst that provides AI assistants with tools and capabilities via the Model Context Protocol. Manage your tasks efficiently with Todo Markdown—CRUD todo lists stored in markdown files, featuring UUID tracking and c It is categorized under productivity. This server exposes 5 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install Todo Markdown in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Todo Markdown is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Todo Markdown MCP Server
An MCP (Model Context Protocol) server that provides todo list functionality backed by a simple markdown file. This server allows AI assistants to manage todo items in a standardized markdown format.
Features
- Markdown-based storage: Todos are stored in a simple
todo.mdfile using standard checkbox syntax - Full CRUD operations: Create, read, update, and delete todo items
- Persistent IDs: Each todo has a unique identifier for reliable updates
- MCP compliance: Follows the Model Context Protocol specification
- TypeScript: Fully typed implementation with comprehensive error handling
- Testing: Complete test suite with Vitest
Installation
From NPM
npm install -g @danjdewhurst/todo-md-mcp
Local Development
- Clone this repository:
git clone https://github.com/danjdewhurst/todo-md-mcp.git cd todo-md-mcp - Install dependencies:
npm install - Build the project:
npm run build
Usage
With Claude Desktop
Add this server to your Claude Desktop configuration:
{
"mcpServers": {
"todo-md": {
"command": "node",
"args": ["/path/to/todo-md-mcp/dist/index.js"]
}
}
}
Or if installed globally via NPM:
{
"mcpServers": {
"todo-md": {
"command": "npx",
"args": ["@danjdewhurst/todo-md-mcp"]
}
}
}
Configuring Todo File Location
By default, the server creates a todo.md file in the current working directory. When using Claude Desktop, this might be a system directory where you don't have write permissions. To specify a custom location for your todo file, use the TODO_FILE_PATH environment variable:
{
"mcpServers": {
"todo-md": {
"command": "npx",
"args": ["@danjdewhurst/todo-md-mcp"],
"env": {
"TODO_FILE_PATH": "/Users/yourname/Documents/todo.md"
}
}
}
}
This solves the common "read-only file system" error by ensuring the todo file is created in a location where you have write permissions.
Recommended locations:
~/Documents/todo.md- Your Documents folder~/Desktop/todo.md- Your Desktop/path/to/your/project/todo.md- Within a specific project
Important: Make sure the directory exists and you have write permissions to the specified location.
Available Tools
The server provides the following MCP tools:
list_todos
Lists all todo items from the markdown file.
Parameters: None
Returns: JSON object with todos array and summary statistics
add_todo
Adds a new todo item.
Parameters:
text(string, required): The todo item text
Returns: The created todo item with generated ID
update_todo
Updates an existing todo item.
Parameters:
id(string, required): The todo item IDtext(string, optional): New text for the todocompleted(boolean, optional): Mark as completed/incomplete
Returns: The updated todo item
delete_todo
Deletes a todo item.
Parameters:
id(string, required): The todo item ID to delete
Returns: Success confirmation
clear_completed
Removes all completed todo items.
Parameters: None
Returns: Number of items cleared
File Format
The server manages a todo.md file in your project root with the following format:
# Todo List
- [ ] First incomplete task <!-- id:550e8400-e29b-41d4-a716-446655440000 -->
- [x] Completed task <!-- id:6ba7b810-9dad-11d1-80b4-00c04fd430c8 -->
- [ ] Another task <!-- id:6ba7b811-9dad-11d1-80b4-00c04fd430c8 -->
<!-- Generated by MCP Todo Server -->
Each todo item includes:
- Standard markdown checkbox syntax (
- [ ]or- [x]) - The todo text
- A hidden HTML comment with a unique ID for tracking
Development
Scripts
npm run build- Build the TypeScript projectnpm run dev- Build and run the servernpm run watch- Watch for changes and rebuildnpm test- Run the test suitenpm run test:watch- Run tests in watch modenpm run lint- Run ESLintnpm run format- Format code with Prettier
Testing
The project includes comprehensive tests covering all functionality:
npm test
Tests cover:
- Markdown parsing and generation
- CRUD operations
- Error handling
- File management
Project Structure
todo-md-mcp/
├── src/
│ ├── index.ts # Main MCP server implementation
│ ├── todoManager.ts # Todo CRUD operations and markdown parsing
│ └── types.ts # TypeScript type definitions
├── tests/
│ └── todoManager.test.ts # Test suite
├── dist/ # Built JavaScript files
├── package.json
├── tsconfig.json
├── .eslintrc.json
├── .prettierrc
├── vitest.config.ts
└── README.md
Requirements
- Node.js 18 or higher
- An MCP-compatible client (like Claude Desktop)
License
MIT
Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests for new functionality
- Run the test suite
- Submit a pull request
Model Context Protocol
This server implements the Model Context Protocol (MCP), an open protocol that standardizes how applications provide context to Large Language Models. MCP enables secure, controlled access to local and remote resources.
For more information about MCP, visit the official documentation.
FAQ
- What is the Todo Markdown MCP server?
- Todo Markdown is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Todo Markdown?
- This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
Todo Markdown is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Piyush G· Sep 9, 2024
We evaluated Todo Markdown against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Useful MCP listing: Todo Markdown is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Sakshi Patil· Jul 7, 2024
Todo Markdown reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend Todo Markdown for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Oshnikdeep· May 5, 2024
Strong directory entry: Todo Markdown surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Dhruvi Jain· Apr 4, 2024
Todo Markdown has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Rahul Santra· Mar 3, 2024
According to our notes, Todo Markdown benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Pratham Ware· Feb 2, 2024
We wired Todo Markdown into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Yash Thakker· Jan 1, 2024
Todo Markdown is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.