{"id":"mutker-mcp-todo-server","name":"mcp-todo-server","homepage":"https://codeberg.org/mutker/mcp-todo-server","repo_url":"https://github.com/mutker/mcp-todo-server","category":"automation","subcategories":[],"tags":["mcp","model-context-protocol","todo","changelog","text-editing","file-system","go"],"what_it_does":"Provides a Model Context Protocol (MCP) server that performs line-based read and edit operations on TODO.md and CHANGELOG.md files, including fetching specific line ranges, applying line-based patches, managing version sections, and importing/generating content.","use_cases":["LLM-assisted maintenance of TODO.md tasks and versioned task sets","Automated generation of CHANGELOG.md entries from completed TODO items","Programmatic line-range retrieval for context-efficient agent workflows","Applying structured edits to changelogs and tasks with atomic multi-file operations"],"not_for":["Serving as a general-purpose document editor across arbitrary formats","Remote multi-user editing without appropriate auth and sandboxing","Use cases requiring network APIs, webhooks, or hosted SaaS guarantees"],"best_when":"You want local (filesystem) TODO/CHANGELOG manipulation via an MCP tool interface where agents can work with line ranges and patches safely within a controlled repo.","avoid_when":"You need strong access control, internet-exposed multi-tenant usage, or a hosted service with SLAs and documented rate limiting.","alternatives":["tumf/mcp-text-editor (inspiration/alternatives for text editing via MCP)","Dedicated code/modification tooling with diff/patch APIs in your existing CI (e.g., git-based automation)","Agent-oriented editors that expose structured file ops via MCP with explicit sandboxing"],"af_score":57.5,"security_score":21.0,"reliability_score":37.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:41:55.835897+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["None specified (local filesystem access implied)"],"oauth":false,"scopes":false,"notes":"No authentication mechanism is described in the provided README; access appears to rely on local execution and filesystem permissions/scope."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source package; no pricing info provided."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":57.5,"security_score":21.0,"reliability_score":37.5,"mcp_server_quality":65.0,"documentation_accuracy":55.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":95.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":20.0,"scope_granularity":0.0,"dependency_hygiene":40.0,"secret_handling":50.0,"security_notes":"Appears to be a local filesystem MCP server (TLS/auth not applicable from README). Main risk is unintended file modification if the server is pointed at the wrong path; ensure sandboxing/least-privilege filesystem permissions. Error handling is claimed but details are not provided in the README.","uptime_documented":0.0,"version_stability":60.0,"breaking_changes_history":40.0,"error_recovery":50.0,"idempotency_support":"false","idempotency_notes":"No explicit idempotency guarantees described for write operations (add/update/import/patch).","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Line-based patching depends on correct line ranges; agents should re-read surrounding context before applying patches.","Without explicit idempotency notes, repeated tool calls may duplicate or corrupt task/version sections if not carefully guarded.","Atomic operations across multiple files are beneficial, but agents should still handle partial failure scenarios cautiously (exact behavior not documented here)."]}}