cd ~

The rtpengine MCP server covers rtpengine, the C media proxy from Sipwise. Each version is an rtpengine release tag, which uses the distinctive mr<a>.<b>.<c>.<d> scheme (e.g. mr26.1.1.2). rtpengine vendors no dependencies, so only its own C source is indexed. Shares this site's OAuth credentials — connect your MCP client at https://webrtc.page/rtpengine.

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.

One registered client works for every server on this site — just point the URL at /rtpengine.

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 \
  rtpengine https://webrtc.page/rtpengine

Claude Code (.mcp.json)

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