2,500+ MCP servers ready to use
Vinkius

Orkes Conductor MCP Server for VS Code Copilot 6 tools — connect in under 2 minutes

Built by Vinkius GDPR 6 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "orkes-conductor": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Orkes Conductor
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.

GitHub Copilot Agent mode brings Orkes Conductor data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Orkes Conductor MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Orkes Conductor

Ask Copilot: "Using Orkes Conductor, help me...". 6 tools available

Why Use VS Code Copilot with the Orkes Conductor MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Orkes Conductor through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Orkes Conductor + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Orkes Conductor MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Orkes Conductor MCP Tools for VS Code Copilot (6)

These 6 tools become available when you connect Orkes Conductor to VS Code Copilot via MCP:

01

get_execution

Get deep state details of a specific Workflow Execution

02

get_workflow_def

Get a specific Workflow Definition explicitly by name

03

list_running

List active, running workflow instances by explicit workflow name

04

list_task_defs

List all explicitly registered Task Definitions via Conductor API

05

list_workflow_defs

List all registered overarching Workflow Definitions via Orkes API

06

search_workflows

Perform an elastic Search across all Workflow executions

Example Prompts for Orkes Conductor in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Orkes Conductor immediately.

01

"Show me all registered workflow definitions."

02

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

03

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

Troubleshooting Orkes Conductor MCP Server with VS Code Copilot

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

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Orkes Conductor + VS Code Copilot FAQ

Common questions about integrating Orkes Conductor MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Orkes Conductor to VS Code Copilot

Get your token, paste the configuration, and start using 6 tools in under 2 minutes. No API key management needed.