MCP.Market

Conductor MCP server

by jarmstrong158·io.github.jarmstrong158/Conductor·v4.0.0
No reviews yet

Local task scheduler and worker manager with MCP integration for Claude Desktop.

B75/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

0 stars32 downloads/wk

Reviews

Write one

Nobody has reviewed Conductor yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Conductor tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 53 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Conductor compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 40% of 1,299 Productivity servers
Downloads a week
32
more than 17% of 427 Productivity servers with a package

Install Conductor in Claude Code, Cursor or VS Code

claude mcp add Conductor -- uvx conductor-mcpserver
Add to Cursor

What the publisher says

From the Conductor repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.jarmstrong158/Conductor -->

Conductor

Claude's hands for local automation — with a web dashboard for the humans who watch it.

Conductor gives Claude direct, persistent control of a local task runner. Tell Claude what you want automated; it creates the scheduled workers, builds multi-step pipelines, wires up email reports, fires test runs, and reads back the logs when something fails — all through conversation. A web dashboard at 127.0.0.1:5000 runs alongside it for humans who want to peek at status, click pause, or hand-edit a worker.

Originally built to automate warehouse reporting workflows (the daily ShipExec metrics pull) and now general-purpose: any Python / batch / shell script, any schedule, any chain.

The MCP server lives in this repo (server.py) — the thin layer that exposes Conductor's REST API as Claude tools. It's bundled and auto-registered on install, so most users won't need to touch it directly. The separate conductor-mcp repo is deprecated — it holds an older copy without the auto-launch race protection.

Claude Integration

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:

  1. Install Conductor (Windows installer or from source)
  2. Conductor writes its MCP entry to Claude Desktop's config on first launch
  3. Restart Claude Desktop once
  4. Claude now controls Conductor through natural language — create workers, build chains, fire tasks, check logs, send emails

Features

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Conductor: common questions

Is Conductor MCP server safe?
Mostly: it is graded B (75/100). Read the Conductor safety report
How do I install Conductor?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Conductor need an API key?
Yes. The registry entry asks for GMAIL_APP_PASSWORD.
Is Conductor maintained?
The last commit was 94 days ago (2026-08-02). The latest release is v4.0.0.
What can I use instead of Conductor?
Servers from other publishers that do the same job: Sheets MCP server.
How does Conductor compare with other Productivity MCP servers?
safety score 75/100 (higher than 40% of 1,299 Productivity servers); downloads a week 32 (more than 17% of 427 Productivity servers with a package). Full comparison.

Alternatives to Conductor

Same job from other publishers: the closest match first, then the best rated.

  • Sheets MCP
    Google Sheets for agent workflows in Claude Code and Claude Desktop: APIs, files, schedules, undo.
    A

More from jarmstrong158 →