How to Use the Conductor (Netflix OSS) MCP in Claude

Q: How do I configure Conductor (Netflix OSS) inside Claude Desktop?

Open your claudedesktopconfig.json file and add the MCP config under the mcpServers block with your Vinkius token. Restart Claude Desktop, look for the hammer icon in the chat input, and you can immediately trigger startworkflow.

Q: How does Claude Desktop handle Conductor (Netflix OSS) task polling?

Claude Desktop uses the polltask and pollbatchtasks tools to check for pending work. The local stdio connection lets the desktop app query your Conductor queues in real-time without timing out.

Q: How do I check queue depth in my chat window?

Ask Claude to run getqueuesize for a specific task type. The agent returns the exact integer count of pending tasks directly in your conversation history.

Q: Does Claude Desktop expose my Conductor task logs to external servers?

No, when Claude Desktop calls gettasklogs through the MCP Server, the log payload is processed locally in your client. Vinkius runs the connector in a secure, zero-trust sandbox, so your internal execution JSON and task logs never touch public training datasets.

Run Netflix Conductor workflows and manage task queues directly from your Claude Desktop chat window.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Conductor (Netflix OSS) MCP to Claude Desktop

Create your Vinkius account to connect Conductor (Netflix OSS) to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Conductor (Netflix OSS) with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run and resume workflows in Claude Desktop

This MCP Server connects your local Claude Desktop app to Netflix Conductor so you can execute, pause, and resume workflows using `execute_workflow`, `pause_workflow`, and `resume_workflow`. You type a quick chat command, and Claude triggers the synchronous run or halts a failing pipeline right from your sidebar. The tool updates your chat with the execution ID immediately. If a task hangs, you tell Claude to run `retry_workflow` or `skip_task` without leaving your workspace to open the Conductor UI.

Bulk workflow operations via MCP Server

This MCP Server exposes batch tools like `bulk_pause`, `bulk_retry`, and `bulk_terminate` to let your agent manage hundreds of failing executions inside Claude Desktop. You paste a list of bad IDs into the chat window, and Claude fires off parallel requests to clean up the queue. Instead of writing custom python cleanup scripts, you let Claude handle the bulk operations. The agent reads the response from `bulk_search` and executes the bulk commands, giving you a summary of terminated or restarted runs in plain text.

Define and validate tasks via MCP Server

This tool suite lets you draft and modify workflow structures using `create_workflow_definition`, `validate_workflow_definition`, and `create_task_definitions`. When you edit a JSON definition in your local directory, Claude reads the file and checks it against your Conductor server. If the schema fails, the agent highlights the exact line in your desktop editor. Once fixed, Claude calls `update_workflow_definitions` to push the schema to production.

Setup guide

Set up Conductor (Netflix OSS) MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Conductor (Netflix OSS) MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Conductor (Netflix OSS) MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under conductor-netflix-oss-mcp.

json

{
  "mcpServers": {
    "conductor-netflix-oss-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Conductor (Netflix OSS). All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Conductor (Netflix OSS) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Conductor (Netflix OSS) MCP in Claude Desktop

Open your `claude_desktop_config.json` file and add the MCP config under the `mcpServers` block with your Vinkius token. Restart Claude Desktop, look for the hammer icon in the chat input, and you can immediately trigger `start_workflow`.

Yes, you can ask Claude Desktop to handle bulk tasks. The agent uses `bulk_restart` or `bulk_terminate` to modify multiple workflow instances at once based on your chat instructions.

Claude Desktop uses the `poll_task` and `poll_batch_tasks` tools to check for pending work. The local stdio connection lets the desktop app query your Conductor queues in real-time without timing out.

Ask Claude to run `get_queue_size` for a specific task type. The agent returns the exact integer count of pending tasks directly in your conversation history.

No, when Claude Desktop calls `get_task_logs` through the MCP Server, the log payload is processed locally in your client. Vinkius runs the connector in a secure, zero-trust sandbox, so your internal execution JSON and task logs never touch public training datasets.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript