mcp-todo

The mcp-todo-server is a Model Context Protocol (MCP) server designed to manage and manipulate TODO.md and CHANGELOG.md files with precise, line-based operations. It offers a focused set of tools to read, patch, and generate changelogs, while supporting multiple line ranges, atomic multi-file changes, and robust encoding support. Typical use cases include extracting current tasks for a specific version, adding or updating tasks and version sections, importing existing task or changelog data, and generating changelog entries from completed tasks. Clients interact with the server via the defined MCP tools such as get-todo-tasks, add-todo-task, update-todo-task, get-changelog, add-changelog-entry, and generate-changelog-from-todo to perform common content and version management operations.

Prerequisites:

• Go 1.23+ installed on your system
• A compatible operating system (Linux, macOS, or Windows)

Installation steps:

1. Ensure Go is installed and in your PATH
   • macOS/Linux: go version
   • Windows: go version
2. Install the MCP server binary: go install codeberg.org/mutker/mcp-todo-server/cmd/mcp-todo-server@latest
3. Verify installation by checking the binary path (GOPATH/bin or Go’s module bin directory) for mcp-todo-server
4. Run the server (example): mcp-todo-server --help

Note: The exact binary path depends on your Go environment configuration. If you encounter permission issues on Unix-like systems, you may need to adjust your PATH or use sudo as appropriate.

Tips:

• The server supports precise line-based edits, reads, and range-based retrievals for efficient interaction with LLM tools.
• Encoding support includes utf-8, shift_jis, latin1, and others; ensure your source files use the intended encoding.
• When applying patches across multiple files, the server attempts to preserve correct line numbers; be aware of insertions or deletions that may affect subsequent ranges.
• Use atomic multi-file operations when updating both TODO.md and CHANGELOG.md to maintain consistency.
• If you run into issues, enable verbose logging or check file permissions to ensure read/write access.
• The server adheres to semantic versioning and keeps a changelog in the repository.