Bring Webrtc
to VS Code Copilot
Learn how to connect LiveKit to VS Code Copilot 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 SubscribersCompatible with every major AI agent and IDE
Gemini
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)
Explicitly trigger a named agent to join a specific room
Provision an ingress point (RTMP, WHIP, or URL pull)
Create a room with specific settings
Map incoming calls to specific rooms based on phone numbers or pins
Define how incoming SIP calls are handled
Define a trunk for dialing out
Dial a SIP number and bring them into a LiveKit room
Remove a dispatch rule
Remove an ingress point
Forcibly disconnect all participants and delete the room
Remove a SIP dispatch rule
Remove a SIP trunk configuration
Get info for a specific participant
List dispatches for a room
List active egress jobs
List provisioned ingresses
List participants in a room
List numbers owned by the project
List active/open rooms
List configured SIP inbound trunks
List configured SIP outbound trunks
Mute/unmute a participant's track
Buy a number and optionally assign a SIP dispatch rule
Release a number back to the inventory
Kick a participant from a room
Search for available numbers by country/area code
Send data packets to participants
Record a specific participant's audio and video
Record an entire room using a web layout
Record one audio and one video track together
Export a single track without transcoding
Record any web page
Stop an active egress
Transfer an active SIP call to another number or URI
Update room or participant settings for a reusable ingress
Change the web layout of an active RoomComposite egress
Update metadata or permissions for a participant
Change the dispatch rule for a number
Update room-wide metadata
Add/remove RTMP/SRT output URLs from an active stream
Subscribe/unsubscribe a participant from specific tracks
Why VS Code Copilot?
GitHub Copilot Agent mode brings LiveKit data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 41 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
LiveKit in VS Code Copilot
LiveKit and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect LiveKit to VS Code Copilot 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.
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 |
Why teams choose Vinkius for LiveKit in VS Code Copilot
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 VS Code Copilot 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.
* 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
How Vinkius secures
LiveKit for VS Code Copilot
Every tool call from VS Code Copilot to the LiveKit MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Prometheus
14 toolsMonitor your infrastructure with Prometheus — run PromQL queries, analyze metrics, and manage time-series data directly from your AI agent.
Conductor (Netflix OSS)
49 toolsAutomate workflow orchestration via Netflix Conductor — manage workflow and task definitions, and start executions directly from any AI agent.
SERPHouse
11 toolsGrant your AI agent unfiltered real-time access to Google and Bing SERP data to scrape organic search results and dynamic pricing.
Clustdoc
6 toolsCollect client documents, track submission progress, and streamline onboarding with organized intake workflows.