Claude DesktopIDE

LiveKit MCP Server

Bring Webrtc
to Claude Desktop

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

Learn how to connect LiveKit to Claude Desktop and start using 41 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Create DispatchCreate IngressCreate RoomCreate Sip Dispatch RuleCreate Sip Inbound TrunkCreate Sip Outbound TrunkCreate Sip ParticipantDelete DispatchDelete IngressDelete RoomDelete Sip Dispatch RuleDelete Sip TrunkGet ParticipantList DispatchList EgressList IngressList ParticipantsList Phone NumbersList RoomsList Sip Inbound TrunkList Sip Outbound TrunkMute Published TrackPurchase Phone NumberRelease Phone NumbersRemove ParticipantSearch Phone NumbersSend DataStart Participant EgressStart Room Composite EgressStart Track Composite EgressStart Track EgressStart Web EgressStop EgressTransfer Sip ParticipantUpdate IngressUpdate LayoutUpdate ParticipantUpdate Phone NumberUpdate Room MetadataUpdate StreamUpdate Subscriptions

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the 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.

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.

How it works

Subscribe to this server
Enter your LiveKit Server URL and API Token/Secret
Start managing your real-time infrastructure from Claude, Cursor, or any MCP-compatible client

No more manual dashboard navigation to check who is in a room or to force-mute a noisy participant. Your AI acts as a real-time session administrator.

Built-in capabilities (41)

create_dispatch

Explicitly trigger a named agent to join a specific room

create_ingress

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

create_room

Create a room with specific settings

create_sip_dispatch_rule

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

create_sip_inbound_trunk

Define how incoming SIP calls are handled

create_sip_outbound_trunk

Define a trunk for dialing out

create_sip_participant

Dial a SIP number and bring them into a LiveKit room

delete_dispatch

Remove a dispatch rule

delete_ingress

Remove an ingress point

delete_room

Forcibly disconnect all participants and delete the room

delete_sip_dispatch_rule

Remove a SIP dispatch rule

delete_sip_trunk

Remove a SIP trunk configuration

get_participant

Get info for a specific participant

list_dispatch

List dispatches for a room

list_egress

List active egress jobs

list_ingress

List provisioned ingresses

list_participants

List participants in a room

list_phone_numbers

List numbers owned by the project

list_rooms

List active/open rooms

list_sip_inbound_trunk

List configured SIP inbound trunks

list_sip_outbound_trunk

List configured SIP outbound trunks

mute_published_track

Mute/unmute a participant's track

purchase_phone_number

Buy a number and optionally assign a SIP dispatch rule

release_phone_numbers

Release a number back to the inventory

remove_participant

Kick a participant from a room

search_phone_numbers

Search for available numbers by country/area code

send_data

Send data packets to participants

start_participant_egress

Record a specific participant's audio and video

start_room_composite_egress

Record an entire room using a web layout

start_track_composite_egress

Record one audio and one video track together

start_track_egress

Export a single track without transcoding

start_web_egress

Record any web page

stop_egress

Stop an active egress

transfer_sip_participant

Transfer an active SIP call to another number or URI

update_ingress

Update room or participant settings for a reusable ingress

update_layout

Change the web layout of an active RoomComposite egress

update_participant

Update metadata or permissions for a participant

update_phone_number

Change the dispatch rule for a number

update_room_metadata

Update room-wide metadata

update_stream

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

update_subscriptions

Subscribe/unsubscribe a participant from specific tracks

Why Claude Desktop?

Claude Desktop is the definitive way to connect LiveKit to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 41 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

—
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
—
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
—
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
—
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

LiveKit in Claude Desktop

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

LiveKit and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect LiveKit to Claude Desktop 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.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	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

Unlock for AI Agents View step-by-step setup guide for Claude Desktop →

Enterprise Security

Why teams choose Vinkius for LiveKit in Claude Desktop

The LiveKit 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 41 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Desktop 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.

Unlock for AI Agents View full LiveKit details →

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

The Vinkius Advantage

How Vinkius secures
LiveKit for Claude Desktop

Every tool call from Claude Desktop to the LiveKit MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

Can I remotely mute a participant who has background noise?

Yes. Use the mute_published_track tool by providing the room name, participant identity, and the specific track SID. You can set the muted boolean to true to silence them immediately.

Is it possible to record a session for later viewing?

Absolutely. You can use start_room_composite_egress to record an entire room using a web layout, or start_web_egress to record a specific URL. These tools leverage LiveKit's Egress service.

How do I kick a disruptive user from a room?

You can use the remove_participant tool. Simply provide the room name and the identity of the participant you wish to disconnect.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).