userSig credentials from your SDK_APP_ID and SECRET_KEY

SECRET_KEY is a sensitive credential. Never commit it to a repository or share it publicly. For local development it's safe to store in your MCP config file — but before going to production, move UserSig generation to your backend. See Generate UserSig on your server..cursor/mcp.json inside your project directory. For a global config that applies to all projects, use ~/.cursor/mcp.json..cursor/mcp.json with the following, and fill in your SDKAPPID and SECRETKEY, and save your changes:{"mcpServers": {"tencent-rtc": {"command": "npx","args": ["-y", "@tencent-rtc/mcp@latest"],"env": {"SDKAPPID": "YOUR_SDKAPPID","SECRETKEY": "YOUR_SECRET_KEY"}}}}


mcpServers section.
{"mcpServers": {"tencent-rtc": {"command": "npx","args": ["-y", "@tencent-rtc/mcp@latest"],"env": {"SDKAPPID": "YOUR_SDKAPPID","SECRETKEY": "YOUR_SECRET_KEY"}}}}

settings.json and configure MCP.
mcpServers section and save the changes.{"mcpServers": {"tencent-rtc": {"command": "npx","args": ["-y", "@tencent-rtc/mcp@latest"],"env": {"SDKAPPID": "YOUR_SDKAPPID","SECRETKEY": "YOUR_SECRET_KEY"}}}}

claude mcp add tencent-rtc -e SDKAPPID=YOUR_SDK_APP_ID -e SECRETKEY=YOUR_SECRET_KEY -- npx -y @tencent-rtc/mcp@latest
~/.claude.json. For project-scoped config, add --scope project — it writes to .mcp.json at your project root.claude mcp list to confirm tencent-rtc appears.codex mcp add tencent-rtc --env SDKAPPID=YOUR_SDK_APP_ID --env SECRETKEY=YOUR_SECRET_KEY -- npx -y @tencent-rtc/mcp@latest
~/.codex/config.toml. For project-scoped config, create .codex/config.toml at your project root.codex mcp list to confirm tencent-rtc appears.Use the tencent-rtc MCP tool to generate a userSig for test001
SDKAppID, userID, and userSig fields.Feedback