CursorIDE

Conductor (Netflix OSS) MCP Server

Bring Workflow Orchestration
to Cursor

Name: Conductor (Netflix OSS) MCP Server
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

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

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

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

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

Subscribe to this server
Enter your Conductor Server URL (e.g., http://conductor-server:8080)
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 Cursor?

Cursor's Agent mode turns Conductor (Netflix OSS) into an in-editor superpower. Ask Cursor to generate code using live data from Conductor (Netflix OSS) and it fetches, processes, and writes. all in a single agentic loop. 49 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

—
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
—
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
—
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
—
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

Conductor (Netflix OSS) in Cursor

AI Agent→Vinkius

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 Cursor 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 catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for Cursor →

Enterprise Security

Why teams choose Vinkius for Conductor (Netflix OSS) in Cursor

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

Unlock for AI Agents View full Conductor (Netflix OSS) details →

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 Cursor

Every tool call from Cursor 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

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.

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.

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.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.