Skip to main content
Glama
noosxe

worker-mcp

by noosxe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to worker-mcp

No user-submitted related servers found.

    Related Servers

    • CacheBash

      rezzedai
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that coordinates AI coding agents with mobile notifications, enabling task queues, inter-agent messaging, session monitoring, and human-in-the-loop approvals.
      MIT

    • agent-comm

      keshrath
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      119 npm
      8
      MIT

    • lxDIG MCP

      lexCoder2
      F
      license
      B
      quality
      C
      maintenance
      MCP server that gives AI coding assistants persistent memory, structural code graph analysis, and safe multi-agent coordination, enabling them to answer architectural questions, track decisions across sessions, and coordinate safely in multi-agent workflows.
      39
      4
      -

    • Kontrol

      B-A-M-N
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that enables AI coding agents to read, edit, search, and run code in local projects with human review loops and policy controls.
      MIT

    • projscan

      abhiyoheswaran1
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides AI coding agents with AST-accurate, context-budget-aware codebase querying, safety gates, and team policy integration via structured tools and a local plugin layer.
      104 npm
      4
      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

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct operation: session lifecycle, command control, action approval, or policy/audit. There is no meaningful overlap between send/cancel, approve/reject, or session management tools.

    Naming Consistency5/5

    All tools use lowercase snake_case verb-first names with clear objects. Session and command tools consistently use the 'pi' prefix, while approval and policy tools use simple verb_noun names, creating a predictable and readable pattern.

    Tool Count5/5

    Ten tools cover the full session lifecycle plus approval and risk-policy management without redundancy. Each tool addresses a concrete need and earns its place in the server.

    Completeness4/5

    The set covers spawning, commanding, cancelling, listing, terminating, approving/rejecting actions, and auditing auto-approved actions. A minor gap is the lack of an explicit tool for retrieving session transcripts or command output if send_pi_command is non-blocking.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources