taskqueue-mcp
Related Servers
Alternatives to taskqueue-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for managing Claude Code conversation sessions1296 npmMIT
- AlicenseAqualityFmaintenanceModel Context Protocol server for Task Management. This allows Claude Desktop (or any MCP client) to manage and execute tasks in a queue-based system.10173 npm215MIT
- AlicenseNot gradedqualityBmaintenanceTask queue MCP server for Claude Code that allows adding, listing, and completing tasks from an external CLI, enabling Claude to drain a queue of follow-up work without disturbing a running turn.MIT
- AlicenseAqualityAmaintenanceMCP server for Claude Code agents to manage persistent shared task boards with dependency graphs, atomic claims, and git-bound tasks.11MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that lets Claude Code dispatch tasks to the LiteLLM gateway, supporting both local Ollama models and Anthropic models via the gateway.-
- FlicenseNot gradedqualityDmaintenanceA flexible MCP server enabling multiple Claude AI sessions to coordinate work across machines through shared state management.1-
TDQS
Scored across 14 tools
Every tool has a clearly distinct purpose targeting specific resources and actions, with no ambiguity. For example, create_project vs. read_project vs. delete_project, and create_task vs. update_task vs. approve_task, each handles a unique operation in the task/project lifecycle.
All tool names follow a consistent verb_noun pattern with snake_case throughout, such as create_project, list_tasks, and update_task. There are no deviations in naming conventions, making the set predictable and readable.
With 14 tools, the count is well-scoped for managing tasks and projects, covering operations from creation to finalization. Each tool earns its place by addressing distinct aspects of the domain without being excessive or insufficient.
The tool set provides complete CRUD/lifecycle coverage for projects and tasks, including creation, reading, updating, deletion, listing, approval, and finalization. There are no obvious gaps, and tools like generate_project_plan and get_next_task enhance workflow support without dead ends.