conductorv2
v2.0 — 15 tools instantly, 80 tools with credentials/Get started

One connection.
Every tool.

Give your AI agent 20+ tools the moment you connect — files, shell, git, and more with zero config. Add credentials to unlock 100+ total tools across cloud, databases, and APIs.

claude_desktop_config.json
{
  "mcpServers": {
    "conductor": {
      "command": "conductor",
      "args": ["mcp", "start"]
    }
  }
}

Works with every major AI coding client

15
zero-config tools
269
tools total
2
GitHub stars
AES-256-GCM
encryption

Live demo

Your AI, fully equipped.

Conductor sits between your AI client and the real world. Every tool call is validated, logged, and — for destructive ops — gated behind user approval before execution.

  • Read and write any file on disk
  • Run shell commands with an allowlist you control
  • Git: status, diff, commit, push — all of it
  • Query any database, inspect schemas
  • Fetch URLs, parse HTML, handle webhooks

Features

Everything in one place

255 Tools

15 tools work instantly with zero config. File system, shell, git, and more. Add credentials to unlock databases, APIs, webhooks, and cloud services.

npm install -g @useconductor/conductor

Security built in

AES-256-GCM encryption, approval gates, circuit breakers, and tamper-evident audit logging — not bolted on.

Zero plaintext secrets. Ever.

One server, all tools

Add one config block to your AI client. That's it. No per-tool servers, no per-tool configs.

Works with any MCP client

Zero config

Install, add the config block, and go. Sensible defaults for everything. Deep config when you need it.

conductor config setup

Webhooks

External systems can trigger Conductor via HTTP. Outgoing events push to any endpoint with retry and HMAC signing.

7 event types · exponential backoff

Full observability

Prometheus metrics, health checks, and SHA-256 chained audit logs. Every tool call recorded permanently.

GET /metrics · GET /audit

Security

Defense-in-depth,
not an afterthought.

Secrets never touch config files. Destructive ops require explicit approval. Every action is logged immutably. No single failure compromises the system.

AES-256-GCM encryption

Secrets are encrypted before storage using AES-256-GCM. Stored in an encrypted local credential store — never in config files.

Approval gates

Destructive tools (shell.exec, filesystem.delete) require explicit user confirmation before execution. Configurable per-tool.

Tamper-evident audit log

SHA-256 chained log at ~/.conductor/audit.log. Every modification breaks the chain — run 'conductor audit verify' to detect tampering.

Circuit breakers

Each tool has an independent circuit breaker. After 5 failures the circuit opens — requests fail fast, no cascading errors.

Command allowlisting

The shell plugin enforces a strict allowlist. No wildcards. No eval(). Only explicitly permitted commands can run.

Rate limiting

All HTTP endpoints are rate-limited. Webhook and tool endpoints have independent limits, configurable per deployment.

How it works

One server. Every client. Every tool.

Your AI client

Claude Desktop
Cursor
Cline
Windsurf
+ more
conductor
MCP server
security pipeline
audit logging
circuit breakers

Tools

filesystem · shell · git
database · web · email
cloud · webhooks · AI
docker · github · slack
+ 90 more

Get started

The last tool setup
you'll ever do.

One command. One config block. Your AI agent gets 20+ tools instantly — files, shell, git, and more. Configure credentials to unlock 100+ total.

npm install -g @useconductor/conductor

Open source · Apache-2.0 License · No vendor lock-in