io.github.jarmstrong158/Conductor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | Anthropic API key for AI Error Analysis |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workersA | List all workers and chains in Conductor. Returns id, name, task_path, schedule, paused state, next trigger time, remaining runs today, last run status, and group assignment for each. |
| create_workerA | Register a new scheduled worker. sched_type: 'fixed' (comma-separated times like '09:00,14:30'), 'interval' (like '2h 30m' or '1h'), or 'cron' (like '0 9 * * 1-5'). timeout_minutes=0 means no timeout. env_vars is KEY=VALUE lines. |
| update_workerB | Update an existing worker by ID. All fields optional except name and task_path which are required. |
| delete_workerA | Delete a worker by ID. Removes from scheduler and database. |
| pause_workerA | Toggle pause/resume for a worker by ID. If paused, resumes it. If running, pauses it. |
| run_worker_nowA | Fire a worker immediately outside its schedule. Logged as MANUAL trigger type. |
| get_worker_historyA | Get the last 10 run history entries for a worker. Returns triggered_at, trigger_type, success, duration_ms, error_msg. |
| pause_all_workersA | Pause all workers at once. |
| delete_all_workersA | Delete ALL workers and chains. Irreversible. Use with caution. |
| list_chainsA | List all task chains. Returns id, name, schedule, steps with stage numbers, stop_on_failure, paused state, next trigger, last run status. |
| create_chainB | Create a new task chain. Steps run sequentially by default. Assign same stage number to multiple steps to run them in parallel. Stage numbers are integers 0-99. |
| run_chain_nowA | Fire a chain immediately outside its schedule. Logged as MANUAL trigger. |
| delete_chainA | Delete a chain and all its steps by ID. |
| get_chain_historyA | Get the last 10 run history entries for a chain. |
| list_groupsA | List all worker groups. Groups are collapsible collections of workers and chains in the dashboard. |
| create_groupC | Create a new worker group. |
| delete_groupA | Delete a group by ID. Unassigns all members but does not delete them. |
| create_worker_from_templateA | Create a worker using a built-in template. Template types: folder_backup (source, dest, keep, summary_email), file_cleanup (folder, pattern, days, summary_email), folder_watcher (watch, rules as [{ext, dest, email_to}]), uptime_check (url, log_file, alert_email), open_url (url), run_and_email (script_path, output_file, email_to). Generated scripts use stdlib only. |
| export_allA | Export all workers, chains, chain steps, and groups as a JSON snapshot. Use for backup or migration. |
| get_logsA | Get debug log entries. Returns entries since a given offset (use 0 for all). Log levels: INFO, OK, FIRE, MANUAL, ERROR, PAUSE, DELETE. Max 500 entries in buffer (oldest drop off). |
| get_statusA | Check Conductor's scheduler and database status. |
| check_for_updateA | Check GitHub for a newer version of Conductor. |
| get_email_settingsA | Check if email credentials are configured. Returns has_credentials (bool) and the sender email address. Use this before any email-related operation to verify setup. If not configured, prompt the user for their Gmail address and App Password. |
| save_email_settingsA | Save Gmail credentials for email notifications and templates. Requires a Gmail address and a Gmail App Password (not the regular password). The user must have 2-Step Verification enabled on their Google account first, then generate an App Password at myaccount.google.com/apppasswords. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
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.
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.
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).
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.