Tencent RTC SDK MCP Server

Tencent RTC SDK MCP Server exposes official Tencent Cloud RTC knowledge and integration capabilities to AI assistants through MCP (Model Context Protocol), helping teams deliver Chat/Call/Live/Room/RTCEngine/TIMPush implementations faster.

Highlights

• Official knowledge retrieval: Quickly locate product docs, integration guides, and best practices.
• Intent-aware routing: Routes by product, platform, and framework to reduce retrieval noise.
• Integration generation support: Supports Web / Android / iOS / Flutter integration entry points.
• MCP compatible: Works with Cursor, CodeBuddy, Codex, Claude, and other MCP clients.

Requirements

• Node.js >= 18
• npm
• Any MCP-capable IDE / AI client

30-Second Quick Start (No console app creation required)

1) Configure MCP Server (Trial mode)

Using Cursor as an example, add this to your project .cursor/mcp.json (or ~/.cursor/mcp.json):

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

2) Confirm server is connected

In your MCP panel, ensure tencent-rtc shows Connected.

3) Explicitly trigger tools

For higher tool activation rate and more stable results, prefix your prompt with @tencent-rtc.

Example:

@tencent-rtc How do I send an audio message when integrating the Web IM SDK in H5?

Full Configuration (Requires creating an app in console)

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

Console entries: https://console.trtc.io

Prerequisites

• No account / no app yet? You can still try first: Start with document retrieval and knowledge Q&A in trial mode.
• SDKAPPID: Your IM/TRTC application ID from Tencent Cloud console.
• SECRETKEY: Used for local/test userSig generation.
• Production requirement: userSig must be generated by your server-side service.

Common Issues

• Connection failed / tool not activated: Verify MCP config and Connected status.
• npx failures: Retry after cache cleanup: rm -rf ~/.npm/_npx && npm cache verify.
• Invalid userSig: Regenerate via get_usersig.

Changelog

Only the latest release is shown here. See CHANGELOG.md for full history.

Version 1.7.8 @2026.09.20

Added

• Added RRF-based BM25 + Dense hybrid retrieval, improving recall and ranking stability for complex natural-language queries.
• Added a vector index build pipeline: integrated build:vectors to generate/update vector indexes during build, enabling semantic recall in the retrieval flow.

Changed

• Optimized pre-framework gating rules: expanded cross-platform query recognition and added English callback / server callback signals, reducing misclassification of server-callback questions as framework-required.
• Enhanced prompt framework detection in preflight-route: added explicit vue/react signals to improve framework completion accuracy in product-only entry scenarios.