MCP server
by danjdewhurst
Manage your tasks efficiently with Todo Markdown—CRUD todo lists stored in markdown files, featuring UUID tracking and c
Manages todo lists stored in markdown files with standard checkbox format. Tracks each item with persistent UUIDs while maintaining human-readable format.
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.
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.
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.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
I recommend Todo Markdown for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated Todo Markdown against two servers with overlapping tools; this profile had the clearer scope statement.
We wired Todo Markdown into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Todo Markdown is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Todo Markdown has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Todo Markdown is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
According to our notes, Todo Markdown benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Todo Markdown is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Todo Markdown reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Strong directory entry: Todo Markdown surfaces stars and publisher context so we could sanity-check maintenance before adopting.
showing 1-10 of 64
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.
todo.md file using standard checkbox syntaxnpm install -g @danjdewhurst/todo-md-mcp
git clone https://github.com/danjdewhurst/todo-md-mcp.git
cd todo-md-mcp
npm install
npm run build
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"]
}
}
}
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 projectImportant: Make sure the directory exists and you have write permissions to the specified location.
The server provides the following MCP tools:
list_todosLists all todo items from the markdown file.
Parameters: None
Returns: JSON object with todos array and summary statistics
add_todoAdds a new todo item.
Parameters:
text (string, required): The todo item textReturns: The created todo item with generated ID
update_todoUpdates an existing todo item.
Parameters:
id (string, required): The todo item IDtext (string, optional): New text for the todocompleted (boolean, optional): Mark as completed/incompleteReturns: The updated todo item
delete_todoDeletes a todo item.
Parameters:
id (string, required): The todo item ID to deleteReturns: Success confirmation
clear_completedRemoves all completed todo items.
Parameters: None
Returns: Number of items cleared
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:
- [ ] or - [x])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 PrettierThe project includes comprehensive tests covering all functionality:
npm test
Tests cover:
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
MIT
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.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.