The janus MCP server covers Janus, the C WebRTC server / gateway from Meetecho. Each version is a janus release tag. Janus vendors no dependencies (OpenSSL, libsrtp, libnice… are system libraries), so only its own C source is indexed. It shares this site's OAuth credentials — connect your MCP client at https://webrtc.page/janus.
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.
The same OAuth applies to all servers — one registered client works for the libwebrtc server (/mcp), the pion server (/pion) and this janus server (/janus); just point the URL at /janus.
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 \ janus https://webrtc.page/janus
--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": {
"janus": {
"type": "http",
"url": "https://webrtc.page/janus",
"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.
| Tag | AST index | Downloaded | Release notes |
|---|---|---|---|
v1.4.1default | indexed | 2026-06-29 | release ↗ |
v1.4.0 | indexed | 2026-06-29 | release ↗ |
v1.3.3 | indexed | 2026-06-29 | release ↗ |
v1.3.2 | indexed | 2026-06-29 | release ↗ |
v1.3.1 | indexed | 2026-06-29 | release ↗ |