4,000+ servers built on vurb.ts
Vinkius
Claude DesktopIDE
Conductor (Netflix OSS) MCP Server

Bring Workflow Orchestration
to Claude Desktop

Learn how to connect Conductor (Netflix OSS) to Claude Desktop and start using 49 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add Task LogBulk PauseBulk RemoveBulk RestartBulk ResumeBulk RetryBulk SearchBulk TerminateCreate Event HandlerCreate Task DefinitionsCreate Workflow DefinitionDelete Event HandlerDelete Task DefinitionDelete Workflow DefinitionExecute WorkflowGet All QueuesGet Correlated WorkflowsGet Event HandlersGet Queue SizeGet Running WorkflowsGet Task DefinitionGet Task DefinitionsGet Task LogsGet WorkflowGet Workflow DefinitionGet Workflow DefinitionsGet Workflow Names And VersionsGet Workflow TasksPause WorkflowPoll Batch TasksPoll TaskRemove WorkflowRequeue TasksRerun WorkflowRestart WorkflowResume WorkflowRetry WorkflowSearch WorkflowsSearch Workflows V2Skip TaskStart WorkflowTerminate WorkflowUpdate Event HandlerUpdate TaskUpdate Task By RefUpdate Task DefinitionUpdate Task V2Update Workflow DefinitionsValidate Workflow Definition

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Conductor (Netflix OSS)

What is the Conductor (Netflix OSS) MCP Server?

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

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.

How it works

  1. Subscribe to this server
  2. Enter your Conductor Server URL (e.g., http://conductor-server:8080)
  3. Start managing your distributed systems from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • DevOps Engineers — quickly inspect and update workflow definitions without navigating the Conductor UI
  • Backend Developers — validate task configurations and trigger test workflows directly from the IDE
  • System Architects — visualize and query the structure of complex distributed processes via natural language

Built-in capabilities (49)

add_task_log

Add a log entry to a task

bulk_pause

Bulk pause workflows

bulk_remove

Bulk remove workflows

bulk_restart

Bulk restart workflows

bulk_resume

Bulk resume workflows

bulk_retry

Bulk retry workflows

bulk_search

Bulk search workflows by ID

bulk_terminate

Bulk terminate workflows

create_event_handler

Create a new event handler

create_task_definitions

Create new task definitions

create_workflow_definition

Create a new workflow definition

delete_event_handler

Delete an event handler

delete_task_definition

Delete a task definition

delete_workflow_definition

Delete a workflow definition

execute_workflow

Execute a workflow (Synchronous)

get_all_queues

Get pending counts for all queues

get_correlated_workflows

Get workflows by correlation ID

get_event_handlers

Get all event handlers

get_queue_size

Get queue depth for a task type

get_running_workflows

Get running workflow IDs by type

get_task_definition

Get a task definition by name

get_task_definitions

Get all task definitions

get_task_logs

Retrieve logs for a task

get_workflow

Get workflow execution by ID

get_workflow_definition

Get a workflow definition by name

get_workflow_definitions

Get all workflow definitions

get_workflow_names_and_versions

Get all workflow names and versions

get_workflow_tasks

Get tasks for a workflow execution

pause_workflow

Pause a workflow

poll_batch_tasks

Long poll for multiple tasks

poll_task

Poll for a single task

remove_workflow

Remove a workflow from the system

requeue_tasks

Requeue pending tasks

rerun_workflow

Rerun a workflow from a specific task

restart_workflow

Restart a workflow from the beginning

resume_workflow

Resume a paused workflow

retry_workflow

Retry the last failed task

search_workflows

Search workflows (returns WorkflowSummary)

search_workflows_v2

Search workflows (returns full Workflow objects)

skip_task

Skip a task in a running workflow

start_workflow

Start a new workflow execution (Asynchronous)

terminate_workflow

Terminate a running workflow

update_event_handler

Update an existing event handler

update_task

Update task result

update_task_by_ref

Update task by reference name

update_task_definition

Update a task definition

update_task_v2

Update task and poll for the next available task

update_workflow_definitions

Create or update workflow definitions (batch)

validate_workflow_definition

Validate a workflow definition without saving

Why Claude Desktop?

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.

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

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

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

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

See it in action

Conductor (Netflix OSS) in Claude Desktop

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Conductor (Netflix OSS) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Conductor (Netflix OSS) to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Conductor (Netflix OSS) in Claude Desktop

The Conductor (Netflix OSS) 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. All 49 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

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

The Vinkius Advantage

How Vinkius secures Conductor (Netflix OSS) for Claude Desktop

Every tool call from Claude Desktop to the Conductor (Netflix OSS) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I check if my workflow JSON is valid without saving it to the server?

Yes! Use the validate_workflow_definition tool. It allows you to submit a workflow definition JSON for validation, and the server will return any structural or logic errors without persisting the changes.

02

How do I see all available workflows and their versions?

You can use the get_workflow_names_and_versions tool to get a high-level list of all registered workflows and their associated version numbers.

03

Is it possible to inspect the configuration of a specific task type?

Yes, use the get_task_definition tool with the specific taskType name. This will return the complete task metadata, including retry logic, timeouts, and input/output keys.

04

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.

05

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.

06

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.

07

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.

08

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.

09

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).

10

Authentication error

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

11

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.

Explore More MCP Servers

View all →