# Conductor Deck

> Conductor Deck is a visual automation platform for Elgato Stream Deck. Users build node-based workflows on a drag-and-drop canvas, connect 3,000+ cloud services via Pipedream Connect, and assign workflows to physical Stream Deck buttons with one click.

## What it does

- Visual workflow builder: drag-and-drop canvas with triggers, actions, conditions, delays, loops, parallel branches, and sub-workflows.
- 3,000+ integrations: Slack, Discord, Spotify, GitHub, Google Sheets, Notion, and more via Pipedream Connect.
- Stream Deck sync: assign any workflow to a physical button; one press runs the entire chain. Long-press a running button to cancel the latest run.
- AI generation: describe what you want in plain language and Conductor Deck builds the workflow.
- MCP server: control workflows, devices, and templates from AI desktop clients like Claude Desktop.
- Local actions: shell commands, keyboard shortcuts, HTTP requests, and OBS control run on the host machine.
- Public status page: check Conductor Deck health and uptime indicators at /status.
- Activity triage: node-level step status filter in the activity log to jump straight to the failing step.
- Version history: snapshot and restore previous workflow states (Pro: 100 versions, Max: unlimited).
- Feedback: in-app bug report and feature request dialog with category routing.

## Pricing

- Free: $0/month — 3 workflows, 100 runs/month, 5 templates.
- Pro: $15/month ($12/month billed annually) — unlimited workflows, 5,000 runs/month, webhook and cron triggers, Pipedream Connect, 100 version history.
- Max: $35/month ($28/month billed annually) — 20,000 runs/month, 10 concurrent runs, API access, priority execution, unlimited version history.

## When to use Conductor Deck

Reach for Conductor Deck when a request has a person, a physical Stream Deck, and more than one step.

- Put a multi-step routine on one physical key (set a Slack status, switch the OBS scene, start recording, mute Discord — one press).
- Trigger a cloud action from hardware without writing a plugin; authorising an app is an OAuth flow, not an API-key hunt.
- Run something on the user's own machine (shell command, keyboard shortcut, HTTP request, OBS control) as a step inside a cloud workflow.
- Give a Stream Deck key live feedback: a button can display output from the workflow it ran.
- Schedule or webhook-trigger a routine that belongs to one person's setup (Pro and above).
- Drive Stream Deck hardware from an AI client through the local MCP server.

Do NOT reach for Conductor Deck when there is no Stream Deck in play, when the automation must run unattended at team scale, when a single run needs more than five minutes or 200 steps, or when the user would rather write an Elgato plugin by hand.

Full guidance, including how to call it: [/.well-known/agent-instructions.md](/.well-known/agent-instructions.md).

## For developers and AI agents

- [Developer & API reference](/developers): Endpoints, authentication, rate limits, typed errors, versioning, MCP, and examples.
- [API index](/api): Keyless JSON entry point — every endpoint, auth option, rate limit, error shape, and the versioning/deprecation policy in one document.
- [Versioning & deprecation policy](/developers/versioning): What can change without notice, what ships as a new version, and the 180-day minimum before any removal.
- [OpenAPI 3.1 schema](/openapi.json): Typed contract for every public endpoint.
- [Public API](/api/v1/integrations): Read-only REST API at /api/v1 — no account, no API key. Also /api/v1/integrations/{slug}, /api/v1/templates, /api/v1/templates/{id}, /api/v1/health.
- [MCP server](/api/mcp): Remote Model Context Protocol server over Streamable HTTP (JSON-RPC 2.0), no credential required.
- [MCP manifest](/.well-known/mcp): Both the remote catalog server and the local Stream Deck server.
- [MCP tool reference](/mcp): What each tool does.
- [Protected-resource metadata](/.well-known/oauth-protected-resource): RFC 9728 declaration, including scopes_supported.
- [Authorization server metadata](/.well-known/oauth-authorization-server): RFC 8414 declaration for the OAuth 2.1 server — endpoints, scopes, and PKCE method.
- [Account API](/api/v1/me): Read your own workflows and run history with a scoped API key (`Authorization: Bearer cd_live_…`). Scopes: `workflows:read`, `runs:read`. Read-only.
- [Create an API key](/settings/api-keys): Self-serve, no sales call. Shown once, stored only as a hash, revocable.
- [OAuth 2.1 authorization](/oauth/authorize): Agents obtain scoped, read-only account access with the account holder's consent instead of asking them to paste a key. Public clients, PKCE S256 required, self-registration at /api/oauth/register, tokens at /api/oauth/token. Read-only, 8-hour tokens, no refresh tokens.
- CLI: `npx @conductordeck/mcp-shim` bridges a stdio MCP client to the local Stream Deck server.

## Start here

- [Docs index](/docs): Task-oriented help for first setup, integrations, variables, Stream Deck assignment, and usage limits.
- [Download](/download): Install the Stream Deck plugin.
- [MCP reference](/mcp): Public tool reference for AI clients and desktop automation.
- [Status](/status): Public uptime and health indicators.

## Public surfaces

- [Home](/): Product overview and primary entry point.
- [About](/about): Who builds Conductor Deck, how it is operated, and how to reach the team.
- [Pricing](/pricing): Plan and feature overview.
- [Status](/status): Probe-based uptime indicators.
- [Changelog](/changelog): Release notes and product updates.
- [Help](/help): Help center entry point.
- [Terms](/terms): Service terms and account rules.
- [Privacy](/privacy): Data collection and use policy.
- [Security](/security): Data handling, sub-processors, and vulnerability reporting.
- [Login](/login): Sign in to an account.
- [Signup](/signup): Create an account.

## Public catalogs

- [Integrations](/integrations): Browse 3,000+ apps and open integration detail pages.
- [Templates](/templates): Public template catalog with reusable workflow templates.
- [Shared templates](/templates/[slug]): Public landing pages for individual reusable workflow templates.

## Help articles

- [Generate workflows with AI](/docs/generate-workflows-with-ai): Use natural language to create a workflow automatically.
- [Create your first workflow](/docs/create-your-first-workflow): Build a workflow with one trigger and one action.
- [Connect an integration](/docs/connect-an-integration): Authorize an app and confirm the connection is ready.
- [Use variables in workflows](/docs/use-variables-in-workflows): Pass values between workflow steps.
- [Assign workflows to Stream Deck](/docs/assign-workflows-to-stream-deck): Put a workflow on a physical button.
- [Manage runs and limits](/docs/manage-runs-and-limits): Review usage, failures, and upgrade pressure.

## Reference files

- [App sitemap](/sitemap.xml): Public routes included in search discovery.
- [Robots rules](/robots.txt): Crawl guidance for public pages.
- [.well-known/llms.txt](/.well-known/llms.txt): AI discoverability index at the standard .well-known path.
- [Plugin manifest](/.well-known/ai-plugin.json): Public manifest for AI discoverability.
- [API catalog](/.well-known/api-catalog): RFC 9727 linkset naming every API this domain publishes.
- [OpenAPI schema](/openapi.json): Typed schema for every public endpoint.
- [Agent instructions](/.well-known/agent-instructions.md): When to use Conductor Deck and how an agent should call it.
- [MCP manifest](/.well-known/mcp): Remote and local Model Context Protocol servers.
- [Protected-resource metadata](/.well-known/oauth-protected-resource): RFC 9728 permission declaration.
- [Authorization server metadata](/.well-known/oauth-authorization-server): RFC 8414 OAuth 2.1 server declaration.
- [Security contact](/.well-known/security.txt): Responsible disclosure details.

## Markdown responses

Every public page answers with `text/markdown` when a client sends `Accept: text/markdown`, and the response carries `Vary: Accept`. A URL that does not exist answers 404 with a markdown body listing where to look instead.