Orkes Conductor

Orkes Conductor MCP Connector for Claude

A+

Orchestrate microservice workflows via Orkes Conductor — list definitions, track running executions, search workflow history, and inspect task states from any AI agent.

6 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Connect your Orkes Conductor cluster to any AI agent and get full visibility into your workflow orchestration layer — definitions, running instances, task states, and execution history.

What you can do

  • Workflow Definitions — List all registered workflow definitions with versions and descriptions, or inspect a specific workflow's graph schema with tasks, operators, and branching logic
  • Task Definitions — List all registered task definitions available for orchestration within your workflows
  • Running Instances — List actively running workflow instances filtered by workflow name to monitor what's currently executing
  • Execution Details — Get deep state details for any workflow execution including input/output mappings, task-by-task trace histories, and exceptions
  • Workflow Search — Search across all workflow executions using Elasticsearch queries, filtering by status, correlation ID, or workflow type

How it works

  1. Subscribe to this server
  2. Enter your Orkes Access Key ID, Access Key Secret, and Base URL
  3. Start monitoring your orchestrations from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Platform engineers — monitor running workflows and quickly identify stuck or failed executions without opening the Conductor UI
  • DevOps teams — search execution history for failure patterns and audit workflow definitions during incident response
  • Architects — inspect workflow graphs and task definitions to understand orchestration dependencies
orchestrationmicroservicesworkflow-enginetask-schedulingexecution-monitoring

6 tools expose this connector's capabilities to your AI agent.

list_workflow_defs

List all registered overarching Workflow Definitions via Orkes API

get_workflow_def

Get a specific Workflow Definition explicitly by name

list_task_defs

List all explicitly registered Task Definitions via Conductor API

list_running

List active, running workflow instances by explicit workflow name

get_execution

Get deep state details of a specific Workflow Execution

search_workflows

Perform an elastic Search across all Workflow executions

See how to talk to your AI agent using Orkes Conductor.

Show me all registered workflow definitions.

Found 12 workflow definitions. 1) 'order-processing' v3 — 8 tasks, including payment validation and shipping triggers. 2) 'user-onboarding' v2 — 5 tasks with email verification fork. 3) 'data-pipeline-daily' v1 — 4 tasks for ETL orchestration. Want me to inspect the graph of any of these?

Are there any failed workflows in the last 24 hours?

Found 3 failed executions in the last 24 hours. 1) order-processing (ID: abc-123) — failed at 'payment-validation' task at 14:23 UTC. Error: 'Gateway timeout'. 2) user-onboarding (ID: def-456) — failed at 'send-welcome-email' at 16:45. Error: 'SMTP connection refused'. 3) data-pipeline-daily (ID: ghi-789) — timed out at 'extract-transform' at 03:12. Want me to get the full execution trace for any?

How many instances of the order-processing workflow are currently running?

8 instances of 'order-processing' currently running. 5 are at the 'payment-validation' stage, 2 at 'shipping-trigger', and 1 at 'inventory-check'. Average execution time so far: 4.2 seconds. No instances are stuck or timed out. Want me to inspect one?

Yes. The search tool 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.

Related Connectors