Skip to main content
Glama
Lalindu0923

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
      A
      maintenance
      Enables centralized management of MCP servers across multiple AI coding harnesses, including adding, removing, monitoring, configuring, and syncing servers with encrypted token storage.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables discovering and managing MCP servers through a registry, supporting listing, searching, and configuration.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Aggregates multiple backend MCP servers into a single unified interface with optional web management UI for tool control and configuration.
      60 npm
      193
      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.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables managing other MCP servers from within Claude Code, including wrapping for reliable restarts, listing, adding, removing, and checking health.
      11
      52 npm
      MIT
    • F
      license
      Not graded
      quality
      F
      maintenance
      MCP server for infrastructure discovery and remote management, enabling SSH command execution, file transfer, log tailing, and machine/service inventory with a companion web dashboard.
      2
      -

    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
    ResponsivenessNo issues