How do I connect my Orkes cluster to my AI client?

You subscribe to the MCP on Vinkius and enter your Orkes credentials, including your Access Key ID, Secret, and Base URL. Once connected, your AI client can immediately start using the capabilities.

Which AI clients can use this MCP?

This MCP works with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

Can I search for specific failed executions?

Yes. You can use the search capability to perform Elasticsearch queries across all workflow executions, filtering by status, correlation ID, or type.

Does this MCP host the connection?

Yes, Vinkius hosts the MCP and manages the connection and credentials so you don't have to run it locally.

Can I see the actual data passed between tasks?

Yes. The get_execution capability provides deep state details, including the specific input and output mappings for each task in a workflow.

Can I search for failed workflows across my entire history?

Yes. The search capability supports Elasticsearch query syntax. search by status (FAILED, TIMED_OUT), workflow type, date ranges, or correlation IDs. Ask your agent 'show me all failed workflows from the last 24 hours' and it returns matching executions with their IDs, failure reasons, and timestamps.

What's the difference between workflow definitions and running instances?

Definitions are the blueprints. the graph schema with tasks, operators, and branching logic. Running instances are actual executions of those definitions, each with their own input data, current state, and task-by-task progress. Think of definitions as classes and instances as objects.

Does this integration support triggering new workflow executions?

Currently, this integration focuses on observability. listing definitions, monitoring running instances, and searching execution history. It does not trigger new workflow executions. For launching workflows, use the Orkes Conductor UI or direct API calls.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Orkes Conductor to ChatGPT, Claude and Gemini

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. Manage and monitor microservice executions from your AI agent.

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.

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.

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 · 6 capabilities

We ship only the actions that matter.

Capability set01 / 02

01-03

3 capabilities in this set.

Part of 6 available through Orkes Conductor.

01
Get execution
This capability pulls deep state details for a specific workflow execution. It provides input and output mappings along with task trace histories.
02
List task defs
This capability retrieves a list of all task definitions registered in your Conductor environment.
03
Get workflow def
This capability fetches a specific workflow definition by its name.

Capability set02 / 02

04-06

3 capabilities in this set.

Part of 6 available through Orkes Conductor.

04
List running
This capability returns a list of active workflow instances, filtered by a specific workflow name.
05
List workflow defs
This capability lists all registered workflow definitions available in your Orkes cluster.
06
Search workflows
This capability runs Elasticsearch queries to search across all workflow executions.

Real work

What teams actually run

Incident Response

Ask your agent to find why a specific workflow failed and get the exact error message immediately.

System Auditing

Use your agent to list all workflow versions and task definitions to verify current configurations.

Live Monitoring

Check the status of active workflows to see how many instances are currently in a specific stage.

Workflow Discovery

Query your cluster to see what workflows are registered and what their logic looks like.

Automate a task

Put Orkes Conductor 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

Orkes Conductor 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.

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

You don't need a client to put Orkes Conductor 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

940ms average. Fast in production.

Orkes Conductor is checked daily against the live service.

Daily averagePeak 1206ms

Oct 3Today

Fastest day: 715ms
Slowest day: 1206ms
14-day trend: Stable0%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 6 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 Orkes Conductor, so you can see the experience inside your AI.

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

Orkes Conductor Connector

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

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

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Orkes Conductor capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "orkes-conductor-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_RrYCpOWyMYAgc2byLtphBnT5DV3QN0zxvc3KjL5z/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 Orkes Conductor in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Orkes Conductor owners hand off.

This MCP is built for engineers managing complex distributed systems who need to move faster during debugging and monitoring.

01
Platform Engineers
They use the agent to identify stuck or failed executions without opening the Conductor UI.
02
DevOps Teams
They use the agent to search execution history for failure patterns during incidents.
03
Architects
They use the agent to inspect workflow graphs and task dependencies.

FAQ

Questions Orkes Conductor owners ask.

01
How do I connect my Orkes cluster to my AI client?
You subscribe to the MCP on Vinkius and enter your Orkes credentials, including your Access Key ID, Secret, and Base URL. Once connected, your AI client can immediately start using the capabilities.
02
Which AI clients can use this MCP?
This MCP works with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.
03
Can I search for specific failed executions?
Yes. You can use the search capability to perform Elasticsearch queries across all workflow executions, filtering by status, correlation ID, or type.
04
Does this MCP host the connection?
Yes, Vinkius hosts the MCP and manages the connection and credentials so you don't have to run it locally.
05
Can I see the actual data passed between tasks?
Yes. The get_execution capability provides deep state details, including the specific input and output mappings for each task in a workflow.
06
Can I search for failed workflows across my entire history?
Yes. The search capability supports Elasticsearch query syntax. search by status (FAILED, TIMED_OUT), workflow type, date ranges, or correlation IDs. Ask your agent 'show me all failed workflows from the last 24 hours' and it returns matching executions with their IDs, failure reasons, and timestamps.
07
What's the difference between workflow definitions and running instances?
Definitions are the blueprints. the graph schema with tasks, operators, and branching logic. Running instances are actual executions of those definitions, each with their own input data, current state, and task-by-task progress. Think of definitions as classes and instances as objects.
08
Does this integration support triggering new workflow executions?
Currently, this integration focuses on observability. listing definitions, monitoring running instances, and searching execution history. It does not trigger new workflow executions. For launching workflows, use the Orkes Conductor UI or direct API calls.

Explore

More in Loved By Devs

Connect Orkes Conductor to Claude, Cursor, ChatGPT & more

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

Each Connector runs inside its own sealed environment.

One switch stops every agent. Instantly.

Spending limits that pause instead of surprise.

We ship only the actions that matter.

01-03

Get execution

List task defs

Get workflow def

04-06

List running

List workflow defs

Search workflows

What teams actually run

Incident Response

System Auditing

Live Monitoring

Workflow Discovery

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

Orkes Conductor Connector

Claude Desktop

Platform Engineers

DevOps Teams

Architects

How do I connect my Orkes cluster to my AI client?

Which AI clients can use this MCP?

Can I search for specific failed executions?

Does this MCP host the connection?

Can I see the actual data passed between tasks?

Can I search for failed workflows across my entire history?

What's the difference between workflow definitions and running instances?

Does this integration support triggering new workflow executions?

GitScrum Tasks AI Connector

Conductor (Netflix OSS) AI Connector

Trigger.dev (Background Tasks & Jobs) AI Connector

Zapier AI Connector

Suggestions

Make (Workflow Automation) AI Connector

Argo Workflows AI Connector

n8n (AI Workflow Automation) AI Connector

AutoGen AI Connector