Conductor
Schedule and run local background tasks and workers from Claude Desktop while optionally emailing you when jobs finish or fail.
Overview
Conductor is a MCP server for the Operate phase that schedules local tasks and manages workers from Claude Desktop, with optional Gmail alerts.
What is this MCP server?
- Local task scheduler and worker manager exposed as conductor-mcpserver (PyPI, stdio)
- MCP integration aimed at Claude Desktop for creating and managing jobs via conversation
- Optional Gmail notifications via GMAIL_USER and GMAIL_APP_PASSWORD environment variables
- Version 0.1.1 PyPI package with MCP 2025-12-11 server schema
- Runs on your machine—no cloud worker fleet required for solo maintenance tasks
- PyPI package conductor-mcpserver at version 0.1.1
- 2 optional secret-backed env vars for Gmail notifications
- stdio MCP transport per server.schema.json 2025-12-11
What problem does it solve?
Builders lose hours re-running scripts, babysitting long jobs, and missing failures because local scheduling is fragmented outside their AI coding workflow.
Who is it for?
Solo developers who want MCP-driven control of local batch jobs, scrapers, and maintenance workers alongside Claude Desktop.
Skip if: Teams that already centralize all jobs in Kubernetes, Temporal, or a managed cloud cron with full observability.
What do I get? / Deliverables
After adding Conductor MCP, Claude can enqueue and supervise local workers and optionally email you so recurring ops work runs without manual cron babysitting.
- MCP-managed schedule of local tasks and worker processes
- Conversation-driven start, stop, and status for maintenance jobs
- Optional email notifications on job outcomes via Gmail SMTP
Recommended MCP Servers
Journey fit
Conductor sits in Operate because it keeps recurring jobs and workers running on your machine after the product code is written. Infra is the right shelf for a local scheduler and worker manager that replaces cron hacks and manual script reruns.
How it compares
Local scheduler MCP integration, not a cloud IaC provisioner or a single-purpose API connector.
Common Questions / FAQ
Who is io.github.jarmstrong158/Conductor for?
Indie builders and Claude Desktop users who need a local task scheduler and worker manager controllable through MCP instead of manual shell and cron setup.
When should I use Conductor MCP?
Use it in Operate when you have recurring local jobs—syncs, reports, data pulls—and want the agent to define schedules and workers without leaving the desktop session.
How do I add Conductor to my agent?
Install conductor-mcpserver from PyPI, configure the MCP server with stdio in Claude Desktop, and set GMAIL_USER and GMAIL_APP_PASSWORD only if you want email notifications.