Can I search for failed workflows across my entire history?

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.

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.

Orkes Conductor MCP Server for Claude Desktop 6 tools — connect in under 2 minutes

Name: Orkes Conductor
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 6 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Orkes Conductor and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "orkes-conductor": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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

About Orkes Conductor MCP Server

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.

Claude Desktop is the definitive way to connect Orkes Conductor to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 6 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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

The Orkes Conductor MCP Server exposes 6 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Orkes Conductor to Claude Desktop via MCP

Follow these steps to integrate the Orkes Conductor MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Orkes Conductor

Look for the 🔌 icon in the chat. your 6 tools are now available

Why Use Claude Desktop with the Orkes Conductor MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Orkes Conductor through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Orkes Conductor + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Orkes Conductor MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Orkes Conductor MCP Tools for Claude Desktop (6)

These 6 tools become available when you connect Orkes Conductor to Claude Desktop via MCP:

get_execution

Get deep state details of a specific Workflow Execution

get_workflow_def

Get a specific Workflow Definition explicitly by name

list_running

List active, running workflow instances by explicit workflow name

list_task_defs

List all explicitly registered Task Definitions via Conductor API

list_workflow_defs

List all registered overarching Workflow Definitions via Orkes API

search_workflows

Perform an elastic Search across all Workflow executions

Example Prompts for Orkes Conductor in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Orkes Conductor immediately.

"Show me all registered workflow definitions."

"Are there any failed workflows in the last 24 hours?"

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

Troubleshooting Orkes Conductor MCP Server with Claude Desktop

Common issues when connecting Orkes Conductor to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Orkes Conductor + Claude Desktop FAQ

Common questions about integrating Orkes Conductor MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.