__        __   _     ____ _____ ____
\ \      / /__| |__ |  _ \_   _/ ___|
 \ \ /\ / / _ \ '_ \| |_) || || |
  \ V  V /  __/ |_) |  _ < | || |___
   \_/\_/ \___|_.__/|_| \_\|_| \____|  MCP Server

Model Context Protocol server for navigating libwebrtc source code

An MCP server that gives AI assistants deep access to the libwebrtc codebase. Supports multiple versions simultaneously, semantic search, RFC lookup, and more.

Free to use for non-commercial purposes.

New here? See recommendations for using Claude →

Grouped by area — open a group for per-tool parameters.

HTTP transport with OAuth 2.1 (PKCE). Dynamic client registration is not supported — register a client first, then pass its client_id (and secret) in your MCP client config. Localhost redirect URIs are allowed for any port.

1. Register a client and grab client_id / client_secret at /profile →

2. Configure your client with those credentials (examples below).

Claude Code — CLI

MCP_CLIENT_SECRET=<your-client-secret> \
claude mcp add --transport http \
  --client-id <your-client-id> --client-secret --callback-port 8090 \
  webrtc https://webrtc.page/mcp

--client-secret reads the secret from MCP_CLIENT_SECRET (or prompts if unset). Without --client-id Claude Code attempts dynamic registration and fails with «does not support dynamic client registration».

Claude Code (.mcp.json)

{
  "mcpServers": {
    "webrtc": {
      "type": "http",
      "url": "https://webrtc.page/mcp",
      "oauth": { "clientId": "<your-client-id>", "callbackPort": 8090 }
    }
  }
}

The secret is kept in your OS keychain, never in .mcp.json. Run the CLI command once to store it, or set MCP_CLIENT_SECRET in the environment.

Claude Desktop (claude_desktop_config.json)  ·  Cursor (.cursor/mcp.json)  ·  Windsurf (~/.codeium/windsurf/mcp_config.json)  ·  VS Code · Zed

These clients connect over the same OAuth flow — supply the registered client_id via each client's own OAuth credentials setting (field names vary by editor). Clients that only support automatic registration cannot connect; use the stdio transport locally instead.

Firefox and Safari ship Google's libwebrtc with their own glue and a local patch stack. These overlays reuse a base milestone's source tree — the table shows which milestone each browser version is based on. Use the browser_versions and overlay_diff tools to explore them.

A second MCP server covers pion, the Go implementation of WebRTC. Each version is a pion/webrtc release tag, indexed together with its go.mod-pinned sibling modules (ice, dtls, sctp, rtp…). It shares this site's OAuth credentials — connect at https://webrtc.page/pion.

198 pion versions indexed →