MCP Gestão de Tarefas
Related Servers
Alternatives to MCP Gestão de Tarefas
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage projects, epics, and tasks with atomic locking, real-time dashboard, and multi-agent coordination.MIT
- AlicenseCqualityCmaintenanceEnables AI agents to manage backlogs via a local API, supporting task and project operations with fail-fast resilience.2210 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides Kanban, Gantt, list views, multi-project management, and archiving for task management via MCP protocol, enabling Cherry Studio Agent to create, update, query, and organize tasks.9 npmISC
- AlicenseBqualityCmaintenanceEnables AI agents to manage tasks through a board with backlog, ready, in-progress, and done columns, plan daily work, track velocity, forecast backlog completion, and leverage rule-based or DeepSeek-powered recommendations.221MIT
- FlicenseNot gradedqualityBmaintenanceGives coding agents 73 native tools to run their own project management — filing, linking, and resolving bugs and features, planning sprints, migrating from Jira/Linear/Shortcut, and handling cross-agent contracts, channels, DMs, notifications, and audit trails. Runs locally or remotely with API-key auth, so agents track work with full intent and reasoning instead of losing it when their context window resets.916 npm1-
- AlicenseAqualityAmaintenanceEnables AI agents to manage tasks on a local-first board via MCP, exposing task creation, updates, and queries through a thin adapter over the REST service.7MIT
TDQS
Scored across 14 tools
Most tools target distinct resources and actions, e.g. project context vs project listing, demand details vs active demand list. Some boundary ambiguity exists between atualizar_subtarefa and concluir_subtarefas, since both can change subtask statuses in bulk, but their primary intents are distinguishable.
All tools follow a consistent verb_noun pattern in Portuguese snake_case (obter_, listar_, criar_, atualizar_, concluir_, etc.). There are no mixed conventions or inconsistent verb styles.
14 tools is well within the appropriate range for a task-management MCP server. Each tool addresses a distinct workflow area: project context, demand lifecycle, subtask management, sprints, and offline/session handling.
The core demand/subtask lifecycle is covered: create, read, update, list, bulk conclude, and sprint association. Minor gaps exist such as no delete/archive operations and no all-demand listing beyond active demands, but these are workable.