The Conductor Deck MCP server lets Claude Desktop, ChatGPT, and Cursor control your Stream Deck: run workflows, push button states, trigger alerts, and browse workflow templates. Five tools have live handlers, while four additional registered tools are discoverable stubs that return structured availability details.
Get Claude Desktop talking to your Stream Deck in three steps.
Download the plugin from conductordeck.com/download and double-click to install. The plugin runs a local-only HTTP server on localhost:47823 that the MCP shim proxies to.
The shim is a thin stdio-to-HTTP bridge that Claude Desktop launches as a subprocess. It auto-updates via npx -y, so you never have to think about versions.
npm install -g @conductordeck/mcp-shimEdit your claude_desktop_config.json (location varies by OS: Claude Desktop has a "Open Config" button under Settings → Developer) and add:
{
"mcpServers": {
"conductor-deck": {
"command": "npx",
"args": ["-y", "@conductordeck/mcp-shim"]
}
}
}Restart Claude Desktop. Nine tools are registered in the MCP server picker: the five available-now tools below have live handlers, and the four planned tools return structured not_implemented_yet responses. Try asking "List my workflows" to confirm the connection.
5 tools shipping in v1.0: all real handlers backed by the production API.
healthHealthv1.0Sanity-check the connection between the AI client, the local Stream Deck plugin, and the Conductor Deck cloud. Returns the linked user, the plugin's local URL, and any troubleshooting hints if the link is broken.
{
"name": "health",
"arguments": {}
}workflowsWorkflowsv1.0Read the linked user's automation workflows. This MCP tool is read-only: list every workflow on the account or fetch a single workflow's full DAG (nodes, edges, triggers, settings). Build or edit workflows through the Conductor Deck app.
listList workflows owned by the linked user (paginated, limit 1–100, default 25).getFetch a single workflow by UUID, including nodes, edges, triggers, and run history.{
"name": "workflows",
"arguments": {
"operation": "list",
"limit": 10
}
}run_workflowRun Workflowv1.0Execute, monitor, and control workflow runs. Supports pass-through `triggerData` so the AI client can hand the workflow real input: chat messages, parsed user intent, anything serializable. Cancel and retry are first-class operations, not afterthoughts.
runStart a new run. Accepts optional `triggerData` (any JSON record) which is interpolated into node configs via `{{trigger.data.field}}`.cancelCancel an in-flight run. Idempotent: safe to call on already-finished runs.retryRetry a failed run from the failed node onward (preserves prior outputs).statusPoll a run's state, per-node statuses, and final output.{
"name": "run_workflow",
"arguments": {
"operation": "run",
"workflowId": "00000000-0000-0000-0000-000000000000",
"triggerData": {
"user_message": "Build failed on main"
}
}
}stream_deckStream Deckv1.0Hardware moatDirect hardware control. Push titles, images, and severity-coded alerts to physical Stream Deck buttons over the local-loopback bridge: no Pipedream, no OAuth, no account linking. The only MCP tool in the ecosystem that talks to the device hardware itself instead of proxying through a cloud account.
list_devicesEnumerate connected Stream Deck devices (model, serial, button grid size).set_buttonSet a button title (max 64 chars) and/or image at a specific row/col.set_alertPush a color-coded alert (critical / warning / info / success) with a 120-char message.clearClear an alert or reset a button to its default state.{
"name": "stream_deck",
"arguments": {
"operation": "set_alert",
"severity": "critical",
"message": "CI build failed on main: last commit: refactor auth"
}
}templatesTemplatesv1.0Browse and instantiate workflow templates from the linked user's library or the public community catalog. Use a template to spin up a working workflow in one call: the AI client hands the user a runnable automation in seconds instead of building one node-by-node.
listList templates. `scope: "user"` (default) returns the linked user's saved templates; `scope: "community"` returns the public catalog.useInstantiate a template into a new workflow on the linked account. Returns the new workflow ID.createSave an existing workflow as a template (1–120 char name, optional 500-char description).shareGenerate a public share link and mark a template public for the community catalog.{
"name": "templates",
"arguments": {
"operation": "list",
"scope": "community"
}
}4 registered stubs document the planned taxonomy. They return a structured `not_implemented_yet` response and point to currently available alternatives where one exists.
build_workflowBuild WorkflowPlannedThis registered tool is not implemented. Build workflows through the AI chat sidebar at conductordeck.com; direct MCP operations for adding, removing, connecting, and configuring nodes remain planned.
add_nodeInsert a trigger / action / condition / delay / loop node into a workflow.remove_nodeDelete a node and its edges, preserving DAG validity.connectAdd an edge between two nodes (validated against the DAG topology).configurePatch a node's config: provider, action, and per-field values.generate_from_descriptionGenerate a complete workflow from a natural-language description.{
"name": "build_workflow",
"arguments": {
"operation": "generate_from_description",
"description": "When my CI build fails, flash the top-left Stream Deck button red and post to #eng-alerts"
}
}connectionsConnectionsPlannedThis registered tool is not implemented and returns `not_implemented_yet`. Manage Pipedream-backed integrations, including Slack, GitHub, Spotify, and 3,000+ more, at conductordeck.com/connections.
listList all connected accounts on the linked user's account.connectInitiate a Pipedream OAuth flow for a given app slug.disconnectRevoke a connected account by ID.{
"name": "connections",
"arguments": {
"operation": "list"
}
}localLocal ActionsPending security reviewThis registered tool is not implemented while direct local actions remain under security review. Build a workflow with a supported local action node and run it through `run_workflow.run`; availability depends on the local app, permissions, and action configuration.
shellRun a shell command (sandboxed, allowlisted).keyboardSend a keyboard shortcut to the active application.httpMake an HTTP request (SSRF-protected, validates against loopback/private IPs).obsCall an OBS WebSocket method (scene change, source toggle, recording control).open_urlOpen a URL in the default browser.notificationDisplay a system notification.{
"name": "local",
"arguments": {
"operation": "obs",
"method": "SetCurrentProgramScene",
"params": { "sceneName": "Starting Soon" }
}
}suggestSuggestPlannedThis registered tool is not implemented. Suggestion cards may be available in the Conductor Deck dashboard when the experimental feature is enabled; a direct MCP suggestions surface remains planned.
workflowsSuggest workflows the user could build given their connected apps and recent activity.integrationsRecommend integrations to connect based on observed workflow patterns.optimizationsIdentify slow / failing / redundant workflows and propose fixes.{
"name": "suggest",
"arguments": {
"operation": "workflows"
}
}Free tier includes 100 workflow runs/month and unlimited AI chat. No credit card.