4,000+ servers built on vurb.ts
Vinkius

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

MCP Inspector GDPR Free for Subscribers

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire LiveKit through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

Ask AI about this MCP Server for Cline

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

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "livekit": {
      "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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
LiveKit
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.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including LiveKit tool calls without waiting for prompts between steps. Connect 41 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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

When Cline 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

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 Cline via MCP

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

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel
02

Add remote server

Click "Add MCP Server" and paste the configuration above
03

Enable the server

Toggle the server switch to ON
04

Start using LiveKit

Ask Cline: "Using LiveKit, help me...". 41 tools available

Why Use Cline with the LiveKit MCP Server

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

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

LiveKit + Cline Use Cases

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

01

Autonomous feature building: tell Cline to fetch data from LiveKit and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use LiveKit tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from LiveKit and generates snapshot tests or mocks based on actual payloads

04

Incident response: query LiveKit for real-time status and let Cline generate hotfix patches based on the findings

Example Prompts for LiveKit in Cline

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

01

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

02

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

03

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

Troubleshooting LiveKit MCP Server with Cline

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

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

LiveKit + Cline FAQ

Common questions about integrating LiveKit MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Explore More MCP Servers

View all →