A
licenseNot graded
qualityB
maintenanceProvides a task passport system for handoff across AI harnesses, enabling users to list, open, create, and checkpoint tasks with stable IDs and verified state.
215 npm
10
MIT
delega-mcp
by delega-dev
Related Servers
Alternatives to delega-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA minimal task management system for LLM agent collaboration via the Model Context Protocol, supporting CRUD operations, task blocking, subtasks, queues, and comments.4 npm1MIT
- AlicenseAqualityAmaintenanceEnables AI agents to publish, claim, submit, and settle tasks with each other, including automatic decomposition of complex work into subtasks assigned to specialized agents. Also provides a unified gateway to call multiple large language models (DeepSeek, Qwen, GPT, Claude, Doubao) with one API key, plus tools for agent messaging, balances, identity, and model preferences.16MIT
agent-taskofficial
FlicenseNot gradedqualityBmaintenanceAgentTask is a governed work platform where human teams and AI agents share one backlog. Hosted remote MCP server (streamable HTTP, OAuth 2.1 or org API keys) with 60+ tools for tasks, subtasks, projects, groups, labels, notes, comments, attachments, search, crews, and agent runs.-- FlicenseNot gradedqualityDmaintenanceEnables AI agents to post real-world tasks, match them to people, and release payments through a delegation-based authorization system that enforces scoped, spend-capped permissions.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage tasks through a structured lifecycle (todo, in_progress, ai_testing, manual_testing, deployment, completed) with human approval gates, providing a single-user task management system with CLI, REST API, and live updates.MIT
TDQS
B3.4/5.0
Scored across 44 tools
Disambiguation4/5
Most tools target distinct resources (tasks, agents, webhooks, automations, recurrences, ingress, context) with clear action boundaries. Some overlap in the claim/lease family (claim_task, heartbeat_task, release_task, set_task_state, complete_task) but descriptions carefully delineate lease vs. state vs. completion. Context tools (get_task_context, update_task_context, get_context_history) could confuse on a quick scan but descriptions separate read/merge/ledger well.
Naming Consistency3/5
Mostly consistent verb_noun pattern (claim_task, list_tasks, create_webhook), but several deviations: 'recall' is a bare verb, 'fleet_attention' is an unusual noun phrase, and 'list_ingress_sources' vs 'create_ingress_source' mix plural/singular conventions for the same resource. Readable but not fully predictable.
Tool Count2/5
44 tools is heavy for a task-queue MCP; the surface spans tasks, agents, projects, stats, webhooks, automations, recurrences, ingress sources, memory/recall, and context ledgers. Many sub-domains are individually well-scoped, but the aggregate exceeds what an agent can comfortably navigate without collisions.
Completeness4/5
Task lifecycle is thorough: create, update, delegate, claim, heartbeat, release, complete, delete, link, comment, chain, context read/write/history, recurrences, and triage. Agent, webhook, automation, and ingress resources each have list/create/update/delete coverage. Minor gaps: no list_task_links companion create path beyond link_task/unlink, and no explicit unlink_task or project create/update/delete despite list_projects.
Maintenance
ActivityActive
ResponsivenessUnresponsive