4,000+ servers built on vurb.ts
Vinkius

Conductor (Netflix OSS) MCP Server for Claude DesktopGive Claude Desktop instant access to 49 tools to Add Task Log, Bulk Pause, Bulk Remove, and more

MCP Inspector GDPR Free for Subscribers

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Ask AI about this MCP Server for Claude Desktop

The Conductor (Netflix OSS) MCP Server for Claude Desktop is a standout in the Industry Titans category — giving your AI agent 49 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "conductor-netflix-oss": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Conductor (Netflix OSS) and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Conductor (Netflix OSS)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Conductor (Netflix OSS) MCP Server

Connect your Netflix Conductor instance to any AI agent to orchestrate complex microservices and workflows through natural conversation.

Claude Desktop is the definitive way to connect Conductor (Netflix OSS) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 49 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

  • Workflow Management — List all registered workflow definitions, fetch specific versions, and manage the lifecycle of your orchestration logic.
  • Task Definitions — Query and manage the underlying task types that power your microservices, ensuring your workers are correctly configured.
  • Validation & Testing — Validate workflow JSON definitions before saving them to the server to prevent runtime errors.
  • Execution Control — Start new workflow instances asynchronously directly from your AI assistant.
  • Batch Operations — Update or create multiple workflow and task definitions in a single request for rapid deployment.

The Conductor (Netflix OSS) MCP Server exposes 49 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 49 Conductor (Netflix OSS) tools available for Claude Desktop

When Claude Desktop connects to Conductor (Netflix OSS) through Vinkius, your AI agent gets direct access to every tool listed below — spanning workflow-orchestration, microservices, netflix-conductor, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add task log on Conductor (Netflix OSS)

Add a log entry to a task

bulk

Bulk pause on Conductor (Netflix OSS)

Bulk pause workflows

bulk

Bulk remove on Conductor (Netflix OSS)

Bulk remove workflows

bulk

Bulk restart on Conductor (Netflix OSS)

Bulk restart workflows

bulk

Bulk resume on Conductor (Netflix OSS)

Bulk resume workflows

bulk

Bulk retry on Conductor (Netflix OSS)

Bulk retry workflows

bulk

Bulk search on Conductor (Netflix OSS)

Bulk search workflows by ID

bulk

Bulk terminate on Conductor (Netflix OSS)

Bulk terminate workflows

create

Create event handler on Conductor (Netflix OSS)

Create a new event handler

create

Create task definitions on Conductor (Netflix OSS)

Create new task definitions

create

Create workflow definition on Conductor (Netflix OSS)

Create a new workflow definition

delete

Delete event handler on Conductor (Netflix OSS)

Delete an event handler

delete

Delete task definition on Conductor (Netflix OSS)

Delete a task definition

delete

Delete workflow definition on Conductor (Netflix OSS)

Delete a workflow definition

execute

Execute workflow on Conductor (Netflix OSS)

Execute a workflow (Synchronous)

get

Get all queues on Conductor (Netflix OSS)

Get pending counts for all queues

get

Get correlated workflows on Conductor (Netflix OSS)

Get workflows by correlation ID

get

Get event handlers on Conductor (Netflix OSS)

Get all event handlers

get

Get queue size on Conductor (Netflix OSS)

Get queue depth for a task type

get

Get running workflows on Conductor (Netflix OSS)

Get running workflow IDs by type

get

Get task definition on Conductor (Netflix OSS)

Get a task definition by name

get

Get task definitions on Conductor (Netflix OSS)

Get all task definitions

get

Get task logs on Conductor (Netflix OSS)

Retrieve logs for a task

get

Get workflow on Conductor (Netflix OSS)

Get workflow execution by ID

get

Get workflow definition on Conductor (Netflix OSS)

Get a workflow definition by name

get

Get workflow definitions on Conductor (Netflix OSS)

Get all workflow definitions

get

Get workflow names and versions on Conductor (Netflix OSS)

Get all workflow names and versions

get

Get workflow tasks on Conductor (Netflix OSS)

Get tasks for a workflow execution

pause

Pause workflow on Conductor (Netflix OSS)

Pause a workflow

poll

Poll batch tasks on Conductor (Netflix OSS)

Long poll for multiple tasks

poll

Poll task on Conductor (Netflix OSS)

Poll for a single task

remove

Remove workflow on Conductor (Netflix OSS)

Remove a workflow from the system

requeue

Requeue tasks on Conductor (Netflix OSS)

Requeue pending tasks

rerun

Rerun workflow on Conductor (Netflix OSS)

Rerun a workflow from a specific task

restart

Restart workflow on Conductor (Netflix OSS)

Restart a workflow from the beginning

resume

Resume workflow on Conductor (Netflix OSS)

Resume a paused workflow

retry

Retry workflow on Conductor (Netflix OSS)

Retry the last failed task

search

Search workflows on Conductor (Netflix OSS)

Search workflows (returns WorkflowSummary)

search

Search workflows v2 on Conductor (Netflix OSS)

Search workflows (returns full Workflow objects)

skip

Skip task on Conductor (Netflix OSS)

Skip a task in a running workflow

start

Start workflow on Conductor (Netflix OSS)

Start a new workflow execution (Asynchronous)

terminate

Terminate workflow on Conductor (Netflix OSS)

Terminate a running workflow

update

Update event handler on Conductor (Netflix OSS)

Update an existing event handler

update

Update task on Conductor (Netflix OSS)

Update task result

update

Update task by ref on Conductor (Netflix OSS)

Update task by reference name

update

Update task definition on Conductor (Netflix OSS)

Update a task definition

update

Update task v2 on Conductor (Netflix OSS)

Update task and poll for the next available task

update

Update workflow definitions on Conductor (Netflix OSS)

Create or update workflow definitions (batch)

validate

Validate workflow definition on Conductor (Netflix OSS)

Validate a workflow definition without saving

Connect Conductor (Netflix OSS) to Claude Desktop via MCP

Follow these steps to wire Conductor (Netflix OSS) into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json
02

Add the MCP Server

Paste the configuration above into the mcpServers section
03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server
04

Start using Conductor (Netflix OSS)

Look for the 🔌 icon in the chat. your 49 tools are now available

Why Use Claude Desktop with the Conductor (Netflix OSS) MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Conductor (Netflix OSS) through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Conductor (Netflix OSS) + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Conductor (Netflix OSS) MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Example Prompts for Conductor (Netflix OSS) in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Conductor (Netflix OSS) immediately.

01

"List all workflow names and their versions currently registered in Conductor."

02

"Show me the full definition for the workflow 'user_onboarding' version 2."

03

"Start a new execution of the 'payment_processing' workflow."

Troubleshooting Conductor (Netflix OSS) MCP Server with Claude Desktop

Common issues when connecting Conductor (Netflix OSS) to Claude Desktop through Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Conductor (Netflix OSS) + Claude Desktop FAQ

Common questions about integrating Conductor (Netflix OSS) MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Explore More MCP Servers

View all →