todo-scout
Related Servers
Alternatives to todo-scout
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that exposes code review tasks from the Fix My Comments VS Code extension to AI agents, enabling them to list, retrieve, reply to, and update task statuses.44 npmMIT
- AlicenseNot gradedqualityDmaintenanceA small MCP server for managing todos, enabling assistants like Claude to create, update, and query task lists through natural conversation. Stores everything in a local SQLite database.13 npm1ISC
- AlicenseNot gradedqualityBmaintenanceMCP server that studies a folder of code repositories, generates markdown documentation (architecture, interfaces, activity), and serves answers over MCP with live ripgrep search and file reads so AI assistants can query codebases and their relationships.7 npmMIT
- FlicenseBqualityDmaintenanceAn MCP server that exposes coding guides and best practices as resources for AI assistants, with GitHub integration, caching, and local file support.1-
- AlicenseAqualityFmaintenanceAn MCP server that allows AI assistants to manage todo lists stored in a simple markdown file, supporting creation, reading, updating, and deletion of todo items with persistent IDs.518 npm6MIT
- AlicenseAqualityBmaintenanceZero-config MCP server that gives AI coding assistants a real-time diagnostic snapshot of your local dev environment. Detects framework, running services, recent errors, git state, and provides a health diagnosis in one call.3532 npm2MIT
TDQS
Scored across 2 tools
The two tools are closely related since todo_stats is essentially an aggregate view of find_todos output, so an agent could occasionally pick the wrong one when it just needs counts vs. full details. However, the descriptions make the distinction reasonably clear: detailed scan vs. per-file counts.
Both names use snake_case, which is consistent, but the conventions differ slightly (verb-first find_todos vs. noun-first todo_stats). Still readable and predictable enough that an agent can infer behavior from the names.
Two tools is thin for a scanning server; a single scan tool with a mode or filter option could plausibly replace both. It is not egregious, but the surface feels minimal and the second tool is a narrow derivative of the first.
The core lifecycle of scanning and summarizing TODOs is covered, but obvious operations are missing: filtering by tag or severity, excluding directories, or scoping to specific file types. Agents can work around some of this client-side, but the surface is notably limited.