An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Conductor (Netflix OSS) to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Orchestrate complex microservice workflows through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 49 capabilities

We ship only the actions that matter.

Capability set01 / 13

01-04

4 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 01

    Bulk pause

    Pauses multiple workflows at once.

  2. 02

    Bulk restart

    Restarts a group of workflows simultaneously.

  3. 03

    Bulk terminate

    Stops multiple running workflows in one command.

  4. 04

    Create event handler

    Sets up a new event handler for your orchestration logic.

Capability set02 / 13

05-08

4 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 05

    Delete event handler

    Removes an existing event handler from the system.

  2. 06

    Delete workflow definition

    Deletes a specific workflow definition.

  3. 07

    Get all queues

    Retrieves the pending counts for every queue in the system.

  4. 08

    Get correlated workflows

    Finds workflows that share a specific correlation ID.

Capability set03 / 13

09-12

4 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 09

    Resume workflow

    Resumes a workflow that was previously paused.

  2. 10

    Retry workflow

    Triggers a retry for the most recent failed task in a workflow.

  3. 11

    Bulk remove

    Deletes multiple workflows from the system in a single request.

  4. 12

    Bulk resume

    Resumes a large group of paused workflows.

Capability set04 / 13

13-16

4 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 13

    Bulk retry

    Retries multiple workflows at once.

  2. 14

    Bulk search

    Searches for multiple workflows using their IDs.

  3. 15

    Create task definitions

    Registers new task definitions for your workers.

  4. 16

    Create workflow definition

    Saves a new workflow definition to the Conductor instance.

Capability set05 / 13

17-20

4 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 17

    Delete task definition

    Removes a task definition from the system.

  2. 18

    Execute workflow

    Runs a workflow synchronously.

  3. 19

    Get queue size

    Checks the current depth of a specific task type queue.

  4. 20

    Get task definition

    Fetches the details of a task definition by its name.

Capability set06 / 13

21-24

4 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 21

    Get workflow

    Retrieves the details of a specific workflow execution by its ID.

  2. 22

    Get workflow names and versions

    Lists all registered workflow names and their associated versions.

  3. 23

    Get workflow tasks

    Fetches all tasks associated with a specific workflow execution.

  4. 24

    Pause workflow

    Pauses a single running workflow.

Capability set07 / 13

25-28

4 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 25

    Poll batch tasks

    Performs a long poll to retrieve multiple tasks.

  2. 26

    Requeue tasks

    Puts pending tasks back into the queue.

  3. 27

    Restart workflow

    Restarts a workflow from the very beginning.

  4. 28

    Search workflows

    Searches for workflows and returns a summary of the results.

Capability set08 / 13

29-32

4 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 29

    Search workflows v2

    Searches for workflows and returns full workflow objects.

  2. 30

    Skip task

    Skips the current task in an active workflow.

  3. 31

    Start workflow

    Starts a new workflow execution asynchronously.

  4. 32

    Terminate workflow

    Stops a running workflow immediately.

Capability set09 / 13

33-36

4 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 33

    Update event handler

    Modifies an existing event handler.

  2. 34

    Update task

    Updates the result of a specific task.

  3. 35

    Validate workflow definition

    Checks a workflow definition for errors without saving it.

  4. 36

    Add task log

    Adds a new log entry to a specific task.

Capability set10 / 13

37-40

4 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 37

    Get event handlers

    Retrieves a list of all event handlers.

  2. 38

    Get running workflows

    Lists the IDs of all currently running workflows for a specific type.

  3. 39

    Get task definitions

    Fetches all task definitions currently in the system.

  4. 40

    Get task logs

    Retrieves the logs for a specific task.

Capability set11 / 13

41-43

3 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 41

    Get workflow definition

    Fetches a specific workflow definition by name.

  2. 42

    Get workflow definitions

    Retrieves all workflow definitions from the server.

  3. 43

    Poll task

    Polls for a single available task.

Capability set12 / 13

44-46

3 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 44

    Remove workflow

    Deletes a specific workflow from the system.

  2. 45

    Rerun workflow

    Reruns a workflow starting from a specific task.

  3. 46

    Update task by ref

    Updates a task using its reference name.

Capability set13 / 13

47-49

3 capabilities in this set.

Part of 49 available through Conductor (Netflix OSS).

  1. 47

    Update task definition

    Modifies an existing task definition.

  2. 48

    Update task v2

    Updates a task and then polls for the next available task.

  3. 49

    Update workflow definitions

    Creates or updates multiple workflow definitions in a batch.

Real work

What teams actually run

01

Rapid Debugging

When a workflow fails, ask your agent to fetch the task logs and retry the specific failed task.

02

Deployment Validation

Before pushing a new microservice logic, have your agent validate the workflow JSON definition.

03

System Maintenance

Use bulk commands to pause all active workflows during a database migration or system update.

04

Real-time Monitoring

Ask your agent for the current queue size of a specific task type to check for worker bottlenecks.

Automate a task

Put Conductor (Netflix OSS) to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Conductor (Netflix OSS) works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Conductor (Netflix OSS) to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1303ms average. Fast in production.

Conductor (Netflix OSS) is checked daily against the live service.

Daily averagePeak 1660ms
Oct 3Today
Fastest day
996ms
Slowest day
1660ms
14-day trend
Slowing+20%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 49 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Conductor (Netflix OSS), so you can see the experience inside your AI.

It does not authenticate your account with Conductor (Netflix OSS). Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Conductor (Netflix OSS) Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_TUjFjxN9H3g5Ba44H63GIIO4Av31lZmg9U3GcY2P/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Conductor (Netflix OSS) capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "conductor-netflix-oss-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_TUjFjxN9H3g5Ba44H63GIIO4Av31lZmg9U3GcY2P/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Conductor (Netflix OSS) in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Conductor (Netflix OSS) owners hand off.

This MCP is built for engineers managing distributed microservices via Netflix Conductor.

  • 01

    DevOps Engineers

    They use the agent to inspect and update definitions without using the Conductor UI.

  • 02

    Backend Developers

    They use the agent to validate task configurations and trigger test workflows from their IDE.

  • 03

    System Architects

    They use the agent to query the structure of complex distributed processes using natural language.

FAQ

Questions Conductor (Netflix OSS) owners ask.

  • 01

    How do I connect this MCP to my Conductor instance?

    After subscribing on Vinkius, you just need to provide your Conductor Server URL. Once connected, your AI client can immediately start interacting with your workflows.

  • 02

    Can I use this with my local Conductor setup?

    Yes, as long as your Conductor instance is reachable via the URL you provide to the MCP, it will work.

  • 03

    Does this replace the Conductor UI?

    It acts as a powerful alternative for common tasks. While the UI is still there, the MCP allows you to perform management and debugging tasks much faster through your AI client.

  • 04

    Can I validate my JSON before I save it?

    Yes, the MCP includes a capability specifically to validate workflow definitions without saving them to the server.

  • 05

    Is it possible to run workflows in bulk?

    Yes, the MCP provides several bulk capabilities to pause, resume, restart, or terminate multiple workflows at once.

  • 06

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

    Yes! Use the validate_workflow_definition capability. 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.

  • 07

    How do I see all available workflows and their versions?

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

  • 08

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

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

Explore

More in Industry Titans

Suggestions

Connect Conductor (Netflix OSS) to Claude, Cursor, ChatGPT & more