productivity

Todo Markdown

danjdewhurst

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.

github stars

5

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Standard markdown checkbox formatPersistent UUID trackingHuman-readable file storage

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

npm version License: MIT Test Lint and Format TypeScript MCP

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.md file 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

  1. Clone this repository:
    git clone https://github.com/danjdewhurst/todo-md-mcp.git
    cd todo-md-mcp
    
  2. Install dependencies:
    npm install
    
  3. 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 ID
  • text (string, optional): New text for the todo
  • completed (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 project
  • npm run dev - Build and run the server
  • npm run watch - Watch for changes and rebuild
  • npm test - Run the test suite
  • npm run test:watch - Run tests in watch mode
  • npm run lint - Run ESLint
  • npm 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

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests for new functionality
  5. Run the test suite
  6. 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 64 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.4 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

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

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

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

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ 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.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.464 reviews
  • Valentina Martinez· Dec 28, 2024

    I recommend Todo Markdown for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Carlos Sethi· Dec 28, 2024

    We evaluated Todo Markdown against two servers with overlapping tools; this profile had the clearer scope statement.

  • Harper Choi· Dec 24, 2024

    We wired Todo Markdown into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Mateo Kim· Dec 24, 2024

    Todo Markdown is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Neel Ramirez· Dec 8, 2024

    Todo Markdown has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Hiroshi Shah· Dec 4, 2024

    Todo Markdown is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Neel Kim· Nov 27, 2024

    According to our notes, Todo Markdown benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Aditi Iyer· Nov 23, 2024

    Todo Markdown is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Rahul Santra· Nov 19, 2024

    Todo Markdown reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Valentina Huang· Nov 19, 2024

    Strong directory entry: Todo Markdown surfaces stars and publisher context so we could sanity-check maintenance before adopting.

showing 1-10 of 64

1 / 7