Skip to main content
Glama
AdityaK9822

polyagent

by AdityaK9822
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to polyagent

No user-submitted related servers found.

    Related Servers

    • Worksona MCP Server by worksona

      Worksona MCP Serverofficial

      worksona
      A
      license
      Not graded
      quality
      D
      maintenance
      Integrates 100+ specialized AI agents with Claude Desktop, providing automated agent discovery, multi-agent coordination, and ready-to-use task templates for complex development and business workflows. Enables users to leverage enterprise-level AI capabilities through actionable resources and intelligent agent matching.
      23 npm
      MIT

    • Claude Swarm MCP Server

      Mayank1805
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables multi-agent orchestration and coordination using specialized, persistent Claude agents for complex workflows like financial analysis and research. It supports intelligent agent handoffs, local storage, and pre-built team templates through Claude Desktop.
      MIT

    • agent-hub

      jalejandrov93
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to offload bounded, read-heavy tasks to external agent CLIs (agy, opencode, copilot) with preflight validation, circuit breakers, and a local dashboard for monitoring delegation and subagent activity.
      19 npm
      Apache 2.0
    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

    A3.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool targets a distinct concern: agent lifecycle, agent execution, pipeline execution, safety configuration, and model discovery. The only potentially similar pair (execute_agent vs execute_pipeline) is clearly differentiated by scope: single agent vs multi-agent pipeline.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern: list_, register_, update_, remove_, execute_, get_, set_. Naming clearly indicates both the action and the resource, with no mixed conventions or vague verbs.

    Tool Count5/5

    Nine tools is well-scoped for an agent management and orchestration server. Each tool covers a necessary aspect of the domain without redundancy or bloat.

    Completeness5/5

    The tool surface provides complete agent lifecycle coverage (list, register, update, remove), execution paths for both individual and multi-agent workflows, safety controls, and model discovery. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources