What can you do with the LiveKit integration?

LiveContext exposes 14 operations on LiveKit, covering participant, room, egress and data message. Common uses include Moderation, Recording and Room state.

LiveContext

All integrations

LiveKit integration

Real-time audio and video communication platform. Create rooms, manage participants, handle recordings, and control media streams. Perfect for video conferencing, live streaming, webinars, and real-time collaboration applications.

14 toolsTokenAPI docs

Connect LiveKit How integrations work

Common LiveKit use cases

Moderation
Recording
Room state
End meetings
Chat messages
End recording
OBS streaming
Start meetings
Role management
Room management

What you can do with LiveKit

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Participant, 4 operations

POSTget_participant
Retrieves details about a specific participant.
POSTlist_participants
Retrieves all participants in a room.
POSTremove_participant
Removes a participant from a room.
POSTupdate_participant
Updates a participant's permissions and metadata.

Room, 4 operations

POSTcreate_room
Creates a new video/audio room.
POSTdelete_room
Closes and deletes a room.
POSTlist_rooms
Retrieves all active video/audio rooms.
POSTupdate_room_metadata
Updates room metadata.

Egress, 3 operations

POSTlist_egress
Lists active and recent egress processes.
POSTstart_room_composite_egress
Starts recording or streaming of a room.
POSTstop_egress
Stops an active recording or stream.

Data message, 1 operation

POSTsend_data
Sends data message to room participants.

Ingress, 1 operation

POSTcreate_ingress
Creates an RTMP or WHIP ingress endpoint.

Track, 1 operation

POSTmute_published_track
Mutes or unmutes a participant's audio/video track.

Use LiveKit from Claude Code, Cursor or Codex

Connect LiveKit in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its LiveKit operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect LiveKit

Create your workspace
Sign up free. Nothing to install.
Connect LiveKit once
Add your LiveKit connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

LiveKit integration FAQ

What can you do with the LiveKit integration?: LiveContext exposes 14 operations on LiveKit, covering participant, room, egress and data message. Common uses include Moderation, Recording and Room state.