LiveKit MCP Server for CursorGive Cursor 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

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Ask AI about this MCP Server for Cursor

Open in ChatGPT Open in Claude Open in Perplexity

The LiveKit MCP Server for Cursor 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": {
      "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.

Cursor's Agent mode turns LiveKit into an in-editor superpower. Ask Cursor to generate code using live data from LiveKit and it fetches, processes, and writes. all in a single agentic loop. 41 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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

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

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

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using LiveKit

Open Agent mode in chat and ask: "Using LiveKit, help me...". 41 tools available

Why Use Cursor with the LiveKit MCP Server

Cursor AI Code Editor provides unique advantages when paired with LiveKit through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

LiveKit + Cursor Use Cases

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

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Example Prompts for LiveKit in Cursor

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

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

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

LiveKit + Cursor FAQ

Common questions about integrating LiveKit MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Explore More MCP Servers

View all →

NVIDIA AI

9 tools

Access LLMs, embeddings, code generation, and reasoning via NVIDIA API Catalog.

UserStack User-Agent Lookup

1 tools

Universal User-Agent intelligence — detect devices, browsers, and OS via AI.

Tomorrow.io Alternative

10 tools

Access hyperlocal weather intelligence — real-time conditions, forecasts, historical archives, severe alerts and route weather from the Tomorrow.io API.

GoHighLevel

10 tools

Equip your AI agent with direct access to GoHighLevel — manage contacts, pipelines, and campaigns without opening the CRM dashboard.