Skip to main content
Glama
Sign In
delega-mcp

delega-mcp

by delega-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to delega-mcp

No user-submitted related servers found.

    Related Servers

    • forge-board

      Ling0925
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and humans to collaborate on tasks via MCP and HTTP, including claiming, updating, commenting, attaching artifacts, managing dependencies, and handling human approvals with shared permissions, leases, versioning, idempotency, and event subscriptions.
      MIT

    • AGTask MCP Server

      Charmly2
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      16
      MIT

    • Team Time MCP

      WorldStoryCm
      A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to discover projects, inspect existing work, atomically claim tasks, record progress, and complete verified work through a task-tracking HTTP API, with version checks, claim coordination, and idempotent retries.
      27
      1
      MIT
    • agent-task

      agent-taskofficial

      AgentTaskLLC
      F
      license
      Not graded
      quality
      C
      maintenance
      AgentTask 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.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 48 tools

    Disambiguation3/5

    Many tools are distinct, but several boundaries are blurry: assign_task vs delegate_task, update_task vs set_task_state, get_task vs get_task_context vs get_context_history, and recall vs context reads all require careful reading. Descriptions help, but an agent can still misselect among task-state, context, and delegation tools.

    Naming Consistency3/5

    Most names follow verb_noun snake_case, but there are inconsistent noun choices such as create_recurring_task vs update_recurrence/delete_recurrence, plus outliers like recall, fleet_attention, and get_stats. The pattern is readable but not uniformly predictable.

    Tool Count2/5

    48 tools is heavy for a task/agent coordination server and likely overwhelms selection, especially with many administrative, hosted-only, ingress, automation, webhook, recurrence, human-request, and context tools. The surface feels like several products combined into one server.

    Completeness4/5

    Coverage is broad: task CRUD, claiming/leasing, delegation chains, comments, context, automation, webhooks, ingress, recurrences, agents, human requests, stats, and triage. Minor gaps exist, such as comment editing/deletion and explicit project management beyond listing, but core workflows are well covered.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources