Skip to main content
Glama
prefrontal-systems

Sub-Agents MCP

by prefrontal-systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Sub-Agents MCP

No user-submitted related servers found.

    Related Servers

    • all-agents-mcp

      Dokkabei97
      A
      license
      B
      quality
      F
      maintenance
      Enables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.
      14
      4 npm
      14
      MIT

    • workbuddy-mcp

      LinHaiJ
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents like Claude Code, Codex, Cursor, and OpenCode to delegate tasks to the WorkBuddy CLI as a sub-agent via an MCP tool, with one-command setup and configurable model/permission options.
      1
      40 npm
      MIT

    • impart-mcp

      J3n5en
      A
      license
      A
      quality
      D
      maintenance
      An agent orchestration layer that wraps expert agents as MCP tools, enabling integration with Claude Desktop, Cursor, and other MCP-compatible environments.
      4
      6 npm
      9
      MIT

    • Statespace

      statespace-tech
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to document data and connect it to AI agents by defining tools and instructions in markdown files. It supports building RAG and text-to-SQL applications that can be deployed as MCP servers, APIs, or CLIs.
      5
      MIT
    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

    A4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'run_agent' has a clearly defined and distinct purpose of delegating complex tasks to autonomous agents.

    Naming Consistency5/5

    The naming pattern cannot be inconsistent with only one tool. The tool name 'run_agent' follows a clear verb_noun pattern, which would be consistent if more tools existed.

    Tool Count2/5

    A single tool is too few for a server named 'Sub-Agents MCP', which implies functionality for managing or interacting with multiple agents. The scope suggests operations like listing agents, checking status, or controlling execution, but only delegation is provided.

    Completeness2/5

    The tool surface is severely incomplete for the implied domain of sub-agent management. While 'run_agent' handles task delegation, there are obvious gaps such as listing available agents, monitoring agent status, terminating agents, or configuring agent parameters, which are essential for a coherent agent management system.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources