Compatible with every major AI agent and IDE
What is the Conductor (Netflix OSS) MCP Server?
Connect your Netflix Conductor instance to any AI agent to orchestrate complex microservices and workflows through natural conversation.
What you can do
- Workflow Management — List all registered workflow definitions, fetch specific versions, and manage the lifecycle of your orchestration logic.
- Task Definitions — Query and manage the underlying task types that power your microservices, ensuring your workers are correctly configured.
- Validation & Testing — Validate workflow JSON definitions before saving them to the server to prevent runtime errors.
- Execution Control — Start new workflow instances asynchronously directly from your AI assistant.
- Batch Operations — Update or create multiple workflow and task definitions in a single request for rapid deployment.
How it works
- Subscribe to this server
- Enter your Conductor Server URL (e.g.,
http://conductor-server:8080) - Start managing your distributed systems from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps Engineers — quickly inspect and update workflow definitions without navigating the Conductor UI
- Backend Developers — validate task configurations and trigger test workflows directly from the IDE
- System Architects — visualize and query the structure of complex distributed processes via natural language
Built-in capabilities (49)
Add a log entry to a task
Bulk pause workflows
Bulk remove workflows
Bulk restart workflows
Bulk resume workflows
Bulk retry workflows
Bulk search workflows by ID
Bulk terminate workflows
Create a new event handler
Create new task definitions
Create a new workflow definition
Delete an event handler
Delete a task definition
Delete a workflow definition
Execute a workflow (Synchronous)
Get pending counts for all queues
Get workflows by correlation ID
Get all event handlers
Get queue depth for a task type
Get running workflow IDs by type
Get a task definition by name
Get all task definitions
Retrieve logs for a task
Get workflow execution by ID
Get a workflow definition by name
Get all workflow definitions
Get all workflow names and versions
Get tasks for a workflow execution
Pause a workflow
Long poll for multiple tasks
Poll for a single task
Remove a workflow from the system
Requeue pending tasks
Rerun a workflow from a specific task
Restart a workflow from the beginning
Resume a paused workflow
Retry the last failed task
Search workflows (returns WorkflowSummary)
Search workflows (returns full Workflow objects)
Skip a task in a running workflow
Start a new workflow execution (Asynchronous)
Terminate a running workflow
Update an existing event handler
Update task result
Update task by reference name
Update a task definition
Update task and poll for the next available task
Create or update workflow definitions (batch)
Validate a workflow definition without saving
Why Mastra AI?
Mastra's agent abstraction provides a clean separation between LLM logic and Conductor (Netflix OSS) tool infrastructure. Connect 49 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.
- —
Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Conductor (Netflix OSS) without touching business code
- —
Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation
- —
TypeScript-native: full type inference for every Conductor (Netflix OSS) tool response with IDE autocomplete and compile-time checks
- —
One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure
Conductor (Netflix OSS) in Mastra AI
Conductor (Netflix OSS) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Conductor (Netflix OSS) to Mastra AI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Conductor (Netflix OSS) in Mastra AI
The Conductor (Netflix OSS) 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. All 49 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Mastra AI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Conductor (Netflix OSS) for Mastra AI
Every tool call from Mastra AI to the Conductor (Netflix OSS) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check if my workflow JSON is valid without saving it to the server?
Yes! Use the validate_workflow_definition tool. It allows you to submit a workflow definition JSON for validation, and the server will return any structural or logic errors without persisting the changes.
How do I see all available workflows and their versions?
You can use the get_workflow_names_and_versions tool to get a high-level list of all registered workflows and their associated version numbers.
Is it possible to inspect the configuration of a specific task type?
Yes, use the get_task_definition tool with the specific taskType name. This will return the complete task metadata, including retry logic, timeouts, and input/output keys.
How does Mastra AI connect to MCP servers?
Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
Can Mastra agents use tools from multiple servers?
Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
Does Mastra support workflow orchestration?
Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.
createMCPClient not exported
Install: npm install @mastra/mcp
Explore More MCP Servers
View all →
Ping Identity
10 toolsManage PingOne user identities, applications, groups, risk policies, and sign-on flows autonomously via AI.

Figshare
20 toolsManage research data and scholarly outputs via Figshare — list public articles, manage private uploads, and organize collections directly from your AI agent.

Maropost
11 toolsAutomate marketing and commerce via Maropost — manage contacts, campaigns, and workflows.

VAT Tax Validator
1 toolsEnsure B2B compliance instantly. Validate European VAT numbers and global Tax IDs using strict local mathematical algorithms.
