LiveKit MCP Server for Claude DesktopGive Claude Desktop 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

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Ask AI about this MCP Server for Claude Desktop

Open in ChatGPT Open in Claude Open in Perplexity

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

Classic Setup·json

{
  "mcpServers": {
    "livekit": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install LiveKit and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

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.

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.

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 Claude Desktop 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 Claude Desktop

When Claude Desktop 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 Claude Desktop via MCP

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

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using LiveKit

Look for the 🔌 icon in the chat. your 41 tools are now available

Why Use Claude Desktop with the LiveKit MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with LiveKit through the Model Context Protocol.

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

LiveKit + Claude Desktop Use Cases

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

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Example Prompts for LiveKit in Claude Desktop

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

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

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).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

LiveKit + Claude Desktop FAQ

Common questions about integrating LiveKit MCP Server with Claude Desktop.

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.