How to Use the Conductor (Netflix OSS) MCP in CrewAI

Q: How do CrewAI agents trigger Conductor (Netflix OSS) tasks?

They use the startworkflow tool to kick off new processes. You just define the workflow name and input parameters in the agent prompt.

Deploy a specialized crew of agents in CrewAI to monitor and operate your Netflix Conductor workflows.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Conductor (Netflix OSS) MCP to CrewAI

Create your Vinkius account to connect Conductor (Netflix OSS) to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Conductor (Netflix OSS) with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Specialized agent collaboration

Assign research agents to analyze workflow history while action agents fix stalled jobs. They work together to maintain system health. Use `search_workflows` to find issues and `rerun_workflow` to resolve them. Your crew coordinates their actions to fix complex bottlenecks.

Autonomous system monitoring

Set up a monitor agent that polls for pending tasks and alerts the team only when necessary. It keeps your operations running around the clock. Use `poll_task` or `get_all_queues` to watch for work. Your agents handle the repetitive polling so you don't have to.

Bulk workflow orchestration

Manage thousands of executions at once by giving your agents bulk control tools. They can clear out stale tasks or restart stuck processes in seconds. Use `bulk_terminate` or `bulk_restart` to handle large volumes of work. Your agents perform these operations based on the criteria you provide.

Setup guide

Set up Conductor (Netflix OSS) MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Conductor (Netflix OSS) tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Conductor (Netflix OSS) Analyst",
    goal="Access and analyze Conductor (Netflix OSS) data via MCP.",
    backstory="Expert analyst with direct Conductor (Netflix OSS) access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Conductor (Netflix OSS) transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Conductor (Netflix OSS) Analyst",
        goal="Access and analyze Conductor (Netflix OSS) data via MCP.",
        backstory="Expert analyst with direct Conductor (Netflix OSS) access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Conductor (Netflix OSS) transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Conductor (Netflix OSS). All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Conductor (Netflix OSS) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Conductor (Netflix OSS) MCP in CrewAI

Include the server URL in your agent definition. CrewAI will load the tools and make them available to your specialized crew members.

They can run complex searches to isolate specific workflow IDs. This allows them to report on current execution statuses accurately.

The server is designed for concurrent access. Multiple agents can poll queues or update tasks simultaneously without conflict.

They use the `start_workflow` tool to kick off new processes. You just define the workflow name and input parameters in the agent prompt.

We isolate all communication via secure, ephemeral connections. Your workflow metadata is never shared or stored outside of your active agent session.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript