Download PDFMarkdown Version
ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Orkes Conductor with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Orchestrate microservice workflows via Orkes Conductor. list definitions, track running executions, search workflow history, and inspect task states from any A

Included with plan

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

Complete set · 6 capabilities

The complete Orkes Conductor capability set.

These are the exact actions your AI can choose when you ask it to work with Orkes Conductor.

Capability set01 / 02

01-03

3 capabilities in this set.

Part of 6 available through Orkes Conductor.

  1. 01

    Get execution

    Get deep state details of a specific Workflow Execution

  2. 02

    List task defs

    List all explicitly registered Task Definitions via Conductor API

  3. 03

    Get workflow def

    Get a specific Workflow Definition explicitly by name

Capability set02 / 02

04-06

3 capabilities in this set.

Part of 6 available through Orkes Conductor.

  1. 04

    List running

    List active, running workflow instances by explicit workflow name

  2. 05

    List workflow defs

    List all registered overarching Workflow Definitions via Orkes API

  3. 06

    Search workflows

    Perform an elastic Search across all Workflow executions

Observed, not estimated

849ms average. Fast in production.

Orkes Conductor is checked daily against the live service.

Daily averagePeak 1137ms
Aug 20Today
Fastest day
668ms
Slowest day
1137ms
14-day trend
Slowing+17%

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.

  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 — 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

FAQ

Questions Orkes Conductor owners ask.

  • 01

    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.

  • 02

    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.

  • 03

    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

Suggestions