LiveKit MCP Server for CrewAIGive CrewAI instant access to 41 tools to Create Dispatch, Create Ingress, Create Room, and more

Name: LiveKit
Price: 29 USD
Availability: InStock
Rating: 0.2 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Connect your CrewAI agents to LiveKit through Vinkius, pass the Edge URL in the `mcps` parameter and every LiveKit tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The LiveKit MCP Server for CrewAI is a standout in the Communication Messaging category — giving your AI agent 41 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="LiveKit Specialist",
    goal="Help users interact with LiveKit effectively",
    backstory=(
        "You are an expert at leveraging LiveKit tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in LiveKit "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 41 available tools "
        "and what they can do."
    ),
)

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

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 LiveKit MCP Server

Connect your LiveKit infrastructure to any AI agent to orchestrate real-time communication environments through natural language. This server provides comprehensive control over WebRTC sessions, participant permissions, and media recording.

When paired with CrewAI, LiveKit becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call LiveKit tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Room Lifecycle — Create, list, and delete rooms with custom timeouts, participant limits, and metadata.
Participant Control — List active participants, retrieve detailed info, or remove users from a session.
Media Management — Remotely mute or unmute specific tracks (audio/video) for any participant.
Real-time Data — Send data packets (Base64 encoded) to specific participants or entire rooms for custom signaling.
Recording & Egress — Start room-wide recordings using web layouts or record specific web pages via the Egress API.
Metadata & Permissions — Update room-wide metadata or modify individual participant permissions and subscriptions on the fly.

The LiveKit MCP Server exposes 41 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 41 LiveKit tools available for CrewAI

When CrewAI connects to LiveKit through Vinkius, your AI agent gets direct access to every tool listed below — spanning webrtc, real-time-audio, real-time-video, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

create

Create dispatch on LiveKit

Explicitly trigger a named agent to join a specific room

create

Create ingress on LiveKit

Provision an ingress point (RTMP, WHIP, or URL pull)

create

Create room on LiveKit

Create a room with specific settings

create

Create sip dispatch rule on LiveKit

Map incoming calls to specific rooms based on phone numbers or pins

create

Create sip inbound trunk on LiveKit

Define how incoming SIP calls are handled

create

Create sip outbound trunk on LiveKit

Define a trunk for dialing out

create

Create sip participant on LiveKit

Dial a SIP number and bring them into a LiveKit room

delete

Delete dispatch on LiveKit

Remove a dispatch rule

delete

Delete ingress on LiveKit

Remove an ingress point

delete

Delete room on LiveKit

Forcibly disconnect all participants and delete the room

delete

Delete sip dispatch rule on LiveKit

Remove a SIP dispatch rule

delete

Delete sip trunk on LiveKit

Remove a SIP trunk configuration

get

Get participant on LiveKit

Get info for a specific participant

list

List dispatch on LiveKit

List dispatches for a room

list

List egress on LiveKit

List active egress jobs

list

List ingress on LiveKit

List provisioned ingresses

list

List participants on LiveKit

List participants in a room

list

List phone numbers on LiveKit

List numbers owned by the project

list

List rooms on LiveKit

List active/open rooms

list

List sip inbound trunk on LiveKit

List configured SIP inbound trunks

list

List sip outbound trunk on LiveKit

List configured SIP outbound trunks

mute

Mute published track on LiveKit

Mute/unmute a participant's track

purchase

Purchase phone number on LiveKit

Buy a number and optionally assign a SIP dispatch rule

release

Release phone numbers on LiveKit

Release a number back to the inventory

remove

Remove participant on LiveKit

Kick a participant from a room

Search phone numbers on LiveKit

Search for available numbers by country/area code

send

Send data on LiveKit

Send data packets to participants

start

Start participant egress on LiveKit

Record a specific participant's audio and video

start

Start room composite egress on LiveKit

Record an entire room using a web layout

start

Start track composite egress on LiveKit

Record one audio and one video track together

start

Start track egress on LiveKit

Export a single track without transcoding

start

Start web egress on LiveKit

Record any web page

stop

Stop egress on LiveKit

Stop an active egress

transfer

Transfer sip participant on LiveKit

Transfer an active SIP call to another number or URI

update

Update ingress on LiveKit

Update room or participant settings for a reusable ingress

update

Update layout on LiveKit

Change the web layout of an active RoomComposite egress

update

Update participant on LiveKit

Update metadata or permissions for a participant

update

Update phone number on LiveKit

Change the dispatch rule for a number

update

Update room metadata on LiveKit

Update room-wide metadata

update

Update stream on LiveKit

Add/remove RTMP/SRT output URLs from an active stream

update

Update subscriptions on LiveKit

Subscribe/unsubscribe a participant from specific tracks

Connect LiveKit to CrewAI via MCP

Follow these steps to wire LiveKit into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 41 tools from LiveKit

Why Use CrewAI with the LiveKit MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with LiveKit through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

LiveKit + CrewAI Use Cases

Practical scenarios where CrewAI combined with the LiveKit MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries LiveKit for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries LiveKit, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain LiveKit tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries LiveKit against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for LiveKit in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with LiveKit immediately.

"List all currently active rooms in my LiveKit instance."

"Create a new room called 'Strategy-Meeting' with a max of 10 participants."

"Mute the audio track for participant 'user_99' in the 'Main-Lobby' room."

Troubleshooting LiveKit MCP Server with CrewAI

Common issues when connecting LiveKit to CrewAI through Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

LiveKit + CrewAI FAQ

Common questions about integrating LiveKit MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.