LiveKit MCP Server for AutoGenGive AutoGen 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

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

Ask AI about this MCP Server for AutoGen

Open in ChatGPT Open in Claude Open in Perplexity

The LiveKit MCP Server for AutoGen 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

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="livekit_agent",
            tools=tools,
            system_message=(
                "You help users with LiveKit. "
                "41 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 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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use LiveKit tools. Connect 41 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

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

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

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

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 41 tools from LiveKit automatically

Why Use AutoGen with the LiveKit MCP Server

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

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

Role-based architecture lets you assign LiveKit 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 LiveKit tool calls

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

LiveKit + AutoGen Use Cases

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

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

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

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

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

Example Prompts for LiveKit in AutoGen

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

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

McpWorkbench not found

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

LiveKit + AutoGen FAQ

Common questions about integrating LiveKit 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 LiveKit 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.