Skip to main content
Glama
RealWorker-Manager MCP Server

RealWorker-Manager MCP Server

by Lalindu0923

Related Servers

Alternatives to RealWorker-Manager MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables centralized management of MCP servers across multiple AI coding harnesses, including adding, removing, monitoring, configuring, and syncing servers with encrypted token storage.
      15 PyPI
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets a lead MCP client delegate text tasks to other LLMs and run CLI coding agents as background jobs, exposing tools to list workers, ask a model synchronously, and check status, read results, or cancel long-running tasks.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables discovering and managing MCP servers through a registry, supporting listing, searching, and configuration.
      -
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables enterprise agent fleets to register workers, dispatch tasks by capability, monitor continuous heartbeat telemetry, trip automated circuit breakers, and recover from checkpointed state through a zero-dependency MCP server.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables centralized management and unified interface for multiple child MCP servers (filesystem, sqlite, etc.), allowing users to discover, launch, and execute tools across different MCP servers through a single gateway.
      -

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools are clearly distinct: list_workers for summaries, get_worker_info for battery/charging, and three system stats variants for different scopes. However, get_worker_info and get_worker_system_stats could be confused if an agent overlooks the specific fields, since system stats may include battery data.

    Naming Consistency4/5

    Tools consistently use verbs (list/get) followed by nouns, and all are snake_case. Minor inconsistency exists in noun phrasing (e.g., get_system_stats_by_location vs get_worker_system_stats vs get_all_workers_system_stats), but the pattern remains predictable overall.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a real-worker management/monitoring domain. Each tool covers a distinct retrieval need, and the count feels neither too sparse nor excessive.

    Completeness4/5

    The server covers core read-only operations: listing workers, getting individual details, and fetching system stats at various granularities. Minor gaps exist, such as no dedicated tool for a specific worker's connection status beyond the list, but agents can work around this by filtering list_workers.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data