VideoSDK MCP Server

The VideoSDK MCP server puts the official documentation inside your AI coding agent. It is hosted at https://docs.videosdk.live/mcp and speaks streamable HTTP. Point your agent at the URL and it can search the docs mid-task.

Every method name it writes then comes from the current page, resolved against the SDK version your project is on.

Install

Run this from your project, or add --scope user to make the server available everywhere:

claude mcp add --transport http videosdk https://docs.videosdk.live/mcp

Confirm it registered with claude mcp list.

Add the server to ~/.gemini/config/mcp_config.json for every project, or to .agents/mcp_config.json for this one:

{
  "mcpServers": {
    "videosdk": {
      "serverUrl": "https://docs.videosdk.live/mcp"
    }
  }
}

A remote server must use serverUrl. The legacy url and httpUrl fields are not supported. Type /mcp in the prompt panel to manage servers from inside the CLI.

Add the server to ~/.codex/config.toml:

[mcp_servers.videosdk]
url = "https://docs.videosdk.live/mcp"

Add the server to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json for this one:

{
  "mcpServers": {
    "videosdk": {
      "url": "https://docs.videosdk.live/mcp"
    }
  }
}

Create .vscode/mcp.json in your workspace:

{
  "servers": {
    "videosdk": {
      "type": "http",
      "url": "https://docs.videosdk.live/mcp"
    }
  }
}

Copilot picks the server up once the file is saved.

Add the server to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "videosdk": {
      "serverUrl": "https://docs.videosdk.live/mcp"
    }
  }
}

Add the server under context_servers in your Zed settings.json:

{
  "context_servers": {
    "videosdk": {
      "source": "custom",
      "url": "https://docs.videosdk.live/mcp"
    }
  }
}

Open the MCP Servers panel, choose to edit the configuration, and add the server to cline_mcp_settings.json:

{
  "mcpServers": {
    "videosdk": {
      "type": "streamableHttp",
      "url": "https://docs.videosdk.live/mcp"
    }
  }
}

Most clients need a restart before a newly added server initialises.

Verify the connection

Ask your agent:

Search the VideoSDK docs for how to generate an auth token, and tell me the page it came from.

A connected agent answers with a real docs.videosdk.live URL it just fetched. If it answers from memory, cites no page, or says it has no such tool, the server has not loaded. Restart the client and check the configuration file you edited.

Example prompts

Name what you want and let the agent fetch the page.

Using the VideoSDK docs, show me how to join a meeting and render remote participant video.

Using the VideoSDK docs, show me how to share a screen.

Using the VideoSDK docs, start an HLS livestream and play the stream back for viewers.

Using the VideoSDK docs, show me how to bring a viewer up on stage mid-stream.

Ask for the version you are actually on

The prompt worth remembering:

We are on the React SDK 0.x.x line. Look up how recording works on that version, not the latest one.

The server resolves the version first, then searches inside it. You get the guide that matches the SDK your project resolved rather than the newest one. Say the SDK line in the prompt whenever your package.json, pubspec.yaml, or Gradle file is not on the current major.

Make the lookup part of the workflow

A rule you state in chat lasts one session. Put it in your repo's agent instructions file and every agent picks it up on every task:

## VideoSDK

Before writing or changing any VideoSDK code, search the VideoSDK docs through the
`videosdk` MCP server and work from the page you get back. Name the SDK and the
version this project resolves. Do not write a method name from memory.

Auth tokens are minted server side. The API secret never appears in client code.

Cursor, Codex, and Copilot read AGENTS.md at the root of the repo. Claude Code reads CLAUDE.md, so paste the same block there. After that, doc lookup happens without you asking for it.

Troubleshooting

The agent says the tools are unavailable. Restart the client. Several of them only initialise MCP servers at startup.

A search comes back empty. Name the SDK explicitly in the prompt. The index is split per SDK, and a query with no platform in it has nothing to narrow on.

A result is wrong or out of date. Ask the agent to send feedback through the server with the SDK, version, and query you used. That reaches the team maintaining the index.

Pair it with the agent skill, which scopes the build and decides what needs looking up.

VideoSDK MCP Server

Install​

Verify the connection​

Example prompts​

Ask for the version you are actually on​

Make the lookup part of the workflow​

Troubleshooting​

Next​