mcp -todotxt

This MCP server implements a Todo.txt integration. It exposes a set of resources and tools that let you interact with a Todo.txt file through the Model Context Protocol (MCP). You can list tasks, filter by context, project, or priority, and perform standard task operations such as adding tasks, marking them as completed, deleting tasks, and updating metadata. The server also provides prompts to summarize tasks or generate new task descriptions, as well as batch operations to perform bulk updates or deletes. Configure the environment by setting the TODO_FILE_PATH to point at your Todo.txt file; if you omit it, the server defaults to a todo.txt in the project root. Interact with the server using MCP-compatible clients to take advantage of the structured prompts, context-aware filtering, and dynamic task management.

Prerequisites:

• Node.js and npm installed on your machine
• Access to the internet to fetch the MCP server package

Install steps:

1. Clone the repository (or skip if you’re using the npm package directly): git clone <repository-url> cd todomcp

2. Install dependencies: npm install

3. Build the project (if applicable): npm run build

4. Start the MCP Todo.txt server: npm start

Optional 1-click run (via npx):

• You can start the server directly with: npx -y guifelix/mcp-server-todotxt@latest This will launch the server and use the default environment variable for the Todo.txt path. You can override with TODO_FILE_PATH if needed.

Environment configuration:

• Set TODO_FILE_PATH to the full path to your Todo.txt file if you don’t want to use the default location.
• Ensure your Todo.txt file is readable and writable by the process running the server.

Tips and notes:

• The server uses the Todo.txt format, so your tasks should follow that convention.
• If you encounter issues locating the Todo.txt file, verify the TODO_FILE_PATH environment variable is correctly set.
• Common commands include adding a task, marking completed, deleting a task, listing tasks with filters, and performing batch updates.
• Dependencies include @modelcontextprotocol/sdk, jsTodoTxt, and zod; keep these updated to stay compatible with MCP protocol changes.
• For development workflows, you can run in dev mode (npm run dev) or run tests (npm test) to validate behavior during changes.