Local task scheduler and worker manager with MCP integration for Claude Desktop.
{
"mcpServers": {
"io-github-jarmstrong158-conductor": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Local task scheduler and worker manager with MCP integration for Claude Desktop.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for io.github.jarmstrong158/Conductor and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Tell Claude what to automate. It handles the rest.
Conductor is a local task orchestration platform that Claude controls directly. Install it, restart Claude Desktop, and Claude can create scheduled workers, build multi-step pipelines, send email reports, and monitor everything — all through conversation. No coding required.

Conductor registers itself as an MCP server in Claude Desktop on first launch. After restarting Claude Desktop once, Claude has 21 tools for full control:
Example conversation:
You: Run my metrics script every night at 8:30 PM and email me the report
Claude: I'll set that up using the Run + Email template. (creates the worker, configures the schedule, wires up Gmail, fires it to test) Done — worker "Daily Metrics Report" is live. Check your email for the test run.
You: That uptime check keeps failing. What's going on?
Claude: (pulls the last 10 runs, reads the error logs) The site returned a 503 three times in the last hour. The SSL certificate expired yesterday. Here's the full error from the last run...
You: Chain my backup script and cleanup script together. Run backup first, then cleanup after it finishes. Every day at 2 AM.
Claude: *(creates a chain with stage 0 = backup, stage 1 = cleanup, cron schedule "0 2 * * ") Chain "Nightly Maintenance" created with 2 steps. Backup runs first, cleanup runs after it succeeds.
How it works:
09:00, 14:30), intervals (2h 30m), or cron expressions (0 9 * * 1-5 with plain-English preview)..py), batch (.bat, .cmd), and shell (.sh) scripts. Selenium and GUI scripts run in a visible terminal window via new_console.KEY=VALUE pairs into subprocess environments.