Skip to main content
Glama
io.github.jarmstrong158/Conductor

io.github.jarmstrong158/Conductor

Related Servers

Alternatives to io.github.jarmstrong158/Conductor

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Give Claude direct access to your AWS account, SSH into your servers, run shell commands on your laptop, query your databases, and manage PM2 processes — all from a Claude chat. No Claude Code subscription needed. Your keys never leave your machine.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables running Claude Code continuously from Telegram, with two-way voice notes, persistent memory across restarts, a self-restarting daemon, and live visibility into every tool call. It lets users drive coding sessions, approve permission prompts, schedule messages, and manage Google Calendar directly from chat.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables building and running visual workflows conversationally inside Claude, orchestrating your existing connector tools step-by-step without storing credentials or owning integrations.
      7 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to run Claude Code remotely through Telegram, with voice-note transcription and spoken replies, persistent memory, scheduled reminders and calendar access, permission approvals, and live tool-call progress. It also supports daemonized 24/7 operation and a session/subagent dashboard.
      MIT

    TDQS

    A3.5/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with worker, chain, group, and system operations cleanly separated. Parallel tools for workers vs chains are explicitly named (e.g., run_worker_now vs run_chain_now), preventing misselection.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern in snake_case, with verbs like list, create, delete, get, run. Minor deviations: 'delete_all_workers' actually deletes chains too (misleading name), and 'run_worker_now' includes a 'now' suffix not present in 'run_chain_now' (though that is also used). Overall predictable.

    Tool Count3/5

    At 24 tools, this sits in the borderline range (16-25) and feels somewhat heavy. The domain is complex (workers, chains, groups, settings, admin), so each tool has a purpose, but the count could be streamlined by combining some operations (e.g., pause_all_workers and delete_all_workers).

    Completeness3/5

    Worker lifecycle is fully covered with list, create, update, delete, pause, run, history, and bulk operations. However, chains lack an update operation and an individual pause/resume toggle, which is a notable gap. Groups also lack update, but that is less critical. Agents can create and run chains but cannot modify them without deleting and recreating.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues