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 AutoGen 6 tools — connect in under 2 minutes

Name: Orkes Conductor
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 6 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Orkes Conductor as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

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.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="orkes_conductor_agent",
            tools=tools,
            system_message=(
                "You help users with Orkes Conductor. "
                "6 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Orkes Conductor tools. Connect 6 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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 AutoGen 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 AutoGen via MCP

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

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 6 tools from Orkes Conductor automatically

Why Use AutoGen with the Orkes Conductor MCP Server

AutoGen provides unique advantages when paired with Orkes Conductor through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Orkes Conductor tools to solve complex tasks

Role-based architecture lets you assign Orkes Conductor tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive Orkes Conductor tool calls

Code execution sandbox: AutoGen agents can write and run code that processes Orkes Conductor tool responses in an isolated environment

Orkes Conductor + AutoGen Use Cases

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

Collaborative analysis: one agent queries Orkes Conductor while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from Orkes Conductor, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using Orkes Conductor data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process Orkes Conductor responses in a sandboxed execution environment

Orkes Conductor MCP Tools for AutoGen (6)

These 6 tools become available when you connect Orkes Conductor to AutoGen 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 AutoGen

Ready-to-use prompts you can give your AutoGen 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 AutoGen

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

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Orkes Conductor + AutoGen FAQ

Common questions about integrating Orkes Conductor MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Orkes Conductor tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.