cd ~

The sipxcom MCP server covers sipXcom / sipxecs, the sipXcom / sipXecs unified-communications stack (its C/C++ components are indexed; Java is not AST-indexed). Each version is a sipxecs release tag. sipxecs vendors no dependencies here, so only its own C/C++ source (sipXtackLib, sipXmediaLib, sipXportLib…) is indexed. It shares this site's OAuth credentials — connect your MCP client at https://webrtc.page/sipxcom.

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 sipxcom server (/sipxcom); just point the URL at /sipxcom.

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

--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": {
    "sipxcom": {
      "type": "http",
      "url": "https://webrtc.page/sipxcom",
      "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.