← Registry

Developer Tools

conductordeck.com

Provides search and retrieval of Conductor Deck integrations and workflow templates for building automations.

2 endpoints10 known toolsFirst detected May 29, 2026Last detected September 6, 2026

ENDPOINT 1

https://www.conductordeck.com/api/mcp

No auth detected

MCP server metadata

Name
conductor-deck
Version
1.0.0
Capabilities
tools
Server instructions

Conductor Deck turns Elgato Stream Deck buttons into multi-step automations. Use these tools to check what Conductor Deck can actually connect to and what it already ships, before you tell a user an automation is possible. search_integrations and get_integration answer "can Conductor Deck talk to <app>, and with which triggers and actions". list_workflow_templates and get_workflow_template answer "does a ready-made workflow already exist for this". get_docs_article answers setup and troubleshooting questions in the product's own words. This server is read-only and needs no credential. Running a workflow or pressing a button happens on the user's own machine through the Stream Deck plugin's local MCP server — see https://www.conductordeck.com/mcp.

Known tools 5

search_integrations

Search the apps Conductor Deck can connect to (Slack, Discord, Spotify, GitHub, Notion, Google Sheets, and thousands more).

Potential side effects
get_integration

Return one app plus the exact triggers and actions a Conductor Deck workflow can use for it.

Inferred read-only
list_workflow_templates

List the built-in, ready-to-use workflow templates.

Inferred read-only
get_workflow_template

Return one built-in template including its node and edge graph, so you can describe exactly what it will build before the user opens it.

Inferred read-only
get_docs_article

Return the full text of one Conductor Deck documentation article.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.conductor-deck]
url = "https://www.conductordeck.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "conductor-deck": {
      "type": "http",
      "url": "https://www.conductordeck.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: conductor-deck
Remote MCP URL: https://www.conductordeck.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "conductor-deck": {
      "url": "https://www.conductordeck.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "conductor-deck": {
      "type": "http",
      "url": "https://www.conductordeck.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "conductor-deck",
  "transport": "streamable-http",
  "url": "https://www.conductordeck.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://www.conductordeck.com/.well-known/mcp

No auth detected

MCP server metadata

Name
conductor-deck
Version
1.0.0
Capabilities
tools
Server instructions

Conductor Deck turns Elgato Stream Deck buttons into multi-step automations. Use these tools to check what Conductor Deck can actually connect to and what it already ships, before you tell a user an automation is possible. search_integrations and get_integration answer "can Conductor Deck talk to <app>, and with which triggers and actions". list_workflow_templates and get_workflow_template answer "does a ready-made workflow already exist for this". get_docs_article answers setup and troubleshooting questions in the product's own words. This server is read-only and needs no credential. Running a workflow or pressing a button happens on the user's own machine through the Stream Deck plugin's local MCP server — see https://www.conductordeck.com/mcp.

Known tools 5

search_integrations

Search the apps Conductor Deck can connect to (Slack, Discord, Spotify, GitHub, Notion, Google Sheets, and thousands more).

Potential side effects
get_integration

Return one app plus the exact triggers and actions a Conductor Deck workflow can use for it.

Inferred read-only
list_workflow_templates

List the built-in, ready-to-use workflow templates.

Inferred read-only
get_workflow_template

Return one built-in template including its node and edge graph, so you can describe exactly what it will build before the user opens it.

Inferred read-only
get_docs_article

Return the full text of one Conductor Deck documentation article.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.conductor-deck]
url = "https://www.conductordeck.com/.well-known/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "conductor-deck": {
      "type": "http",
      "url": "https://www.conductordeck.com/.well-known/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: conductor-deck
Remote MCP URL: https://www.conductordeck.com/.well-known/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "conductor-deck": {
      "url": "https://www.conductordeck.com/.well-known/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "conductor-deck": {
      "type": "http",
      "url": "https://www.conductordeck.com/.well-known/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "conductor-deck",
  "transport": "streamable-http",
  "url": "https://www.conductordeck.com/.well-known/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.