Skip to main content
Glama
rputasi

mcp-swarm-router

by rputasi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-swarm-router

No user-submitted related servers found.

    Related Servers

    • subway-mcp-server

      MauricioPerera
      A
      license
      A
      quality
      B
      maintenance
      Local MCP server that exposes delegation tools for Codex, Claude, and Antigravity CLI, enabling an orchestrator agent to assign tasks to these sub-agents via non-interactive CLI commands.
      3
      MIT

    • mcp-server-subagent

      dvcrn
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that allows a planning agent to delegate tasks to executor agents (e.g., Claude Code, Aider) with bi-directional communication and real-time log streaming.
      11
      15
      AGPL 3.0

    • MCP Plus

      David3u
      F
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that enhances AI agents with tools for codebase analysis, task delegation to sub-agents, multi-agent coordination through chatrooms, and project todo management.
      -

    • opencode-mcp-bridge

      Dheerax
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that lets any AI tool delegate tasks to the OpenCode CLI as a subagent, with multi-session orchestration, event tracking, and task contracts.
      28
      10
      1
      MIT

    • delegations-mcp

      kaijfox
      F
      license
      B
      quality
      D
      maintenance
      An MCP server that exposes a library of delegation prompts to orchestrate tasks between a primary LLM and specialized sub-agents. It enables the execution of self-contained, bounded tasks with built-in support for configuration discovery and project-specific delegation libraries.
      3
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one provides an inventory of available agents, the other executes a task with a specified agent. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern (get_agent_roster, delegate_task), using snake_case and clear action verbs. The naming is uniform and predictable.

    Tool Count3/5

    With only 2 tools, the set is on the thin side but still covers the core workflow of a router: discovering agents and delegating to them. It feels slightly sparse for a 'swarm' concept, but each tool is essential.

    Completeness4/5

    The tool pair covers the full delegation lifecycle needed: learn who is available, then execute a task. Missing features like parallel delegation or cancellation are minor gaps for a simple router implementation, and agents can work around them by calling delegate_task repeatedly.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources