@tencent-rtc/mcp 1.6.4 → 1.6.5

package/server.js

@@ -3,40 +3,40 @@ import { registryTools } from './tools/index.js';
 const SERVER_INSTRUCTIONS = `
 You are using Tencent RTC MCP Server for SDK documentation retrieval.
 
-- search_trtc_knowledge: Primary tool for Tencent RTC / Chat(IM) / Push(TIMPush) documentation lookup.
-  Covers: Chat UIKit, CallKit, LiveKit, RoomKit, TRTC Native SDK, WebRTC / rtcEngine, TIMPush.
-  Use this tool first for documentation lookup, FAQ, error code, API reference, feature discovery, and troubleshooting.
-  Do not use web_search for questions that can be answered by this knowledge base.
+- search_trtc_knowledge: Primary tool for searching Tencent RTC / Chat(IM) / Push(TIMPush) product documentation.
+  Covers: Chat UIKit, CallKit, LiveKit, RoomKit, TRTC Native SDK, WebRTC/rtcEngine, TIMPush.
+  Use this tool FIRST for all technical documentation / FAQ / error code / integration guide lookups.
+  Do NOT use web_search for questions that can be answered via this knowledge base.
 
-**Product routing (before calling search_trtc_knowledge, infer the product array first):**
-- TIMPush / push / notification / offline push / vendor channel / FCM / APNs / Huawei / Xiaomi / OPPO / vivo -> product=["push"] (standalone product; do not misroute to chat)
-- conversation / TUIKit / ChatKit / IM component / theme customization -> ["chat"]
-- CallKit / calling -> ["call"]; LiveKit / live streaming / voice room -> ["live"]; RoomKit / meeting -> ["room"]
-- TRTC Web SDK / rtcengine / WebRTC plugin -> ["rtcengine"]
-- TRTCCloud / native client SDK -> ["native_trtc_sdk"]
-- If both push and IM are involved, product can be ["push","chat"]
-- If the product cannot be inferred uniquely, ask the user first. Do not hard-search without product and do not use web_search.
+**Product routing（调用 search_trtc_knowledge 前 MUST 推断 product 数组）**：
+- TIMPush / 推送 / 厂商通道 / FCM / APNs / 华为 / 小米 / OPPO / vivo → product=["push"]（独立产品，禁止误归 chat）
+- 会话 / TUIKit / ChatKit / IM 组件 / 主题定制 → ["chat"]
+- CallKit / 通话 → ["call"]；直播 / 语聊房 / LiveKit → ["live"]；RoomKit / 会议 → ["room"]
+- TRTC Web SDK / rtcengine / WebRTC 插件 → ["rtcengine"]
+- TRTCCloud / Native SDK（客户端）→ ["native_trtc_sdk"]
+- 推送 + IM 同时涉及 → 可传 ["push","chat"]
+- 无法从 prompt 唯一判断 product → 先向用户确认，不要无 product 硬搜，也不要 web_search
 
-**Framework**: If search_trtc_knowledge returns needs_framework, you must call present_framework_choice first and then retry. Follow the decision table in the search_trtc_knowledge tool description.
-**When in doubt**: Still prefer search_trtc_knowledge with the best product guess; clarify or retry when status is empty or low_confidence.
+**Frameworks**：返回 needs_framework 时 MUST 先 present_framework_choice；详见 search_trtc_knowledge 工具 description 决策表。
+**When in doubt**：仍优先调用 search_trtc_knowledge（带最佳猜测 product）；status=empty 或 low_confidence 时再澄清或重搜。
 
-**queryID rule (hard requirement, required for CLS continuity):**
-- First search_trtc_knowledge call: do not pass queryID (or pass an empty string). The response will contain a server-generated queryID.
-- Every later search_trtc_knowledge / finalize_answer / submit_feedback call in the same consultation must pass that same queryID.
-- Omitting queryID starts a new consultation chain and breaks CLS continuity.
-- If the user asks follow-up sub-questions, keep using the same queryID.
+**queryID 传递规则（硬规则，违反会导致 CLS 数据断裂）**：
+- 首次调用 search_trtc_knowledge：无需传 queryID（默认空串），响应 JSON 中会有 server 生成的 queryID 字段
+- 后续每一次 search_trtc_knowledge / finalize_answer / submit_feedback 调用：**MUST** 携带首次响应中的 queryID
+- 不传 queryID = 视为全新咨询（CLS 数据无法串联）
+- 多 sub-question 迭代搜索时，每次都要带相同的 queryID
 
 Workflow:
 1. Call search_trtc_knowledge. Reuse the same queryID for all retries/searches in this consultation.
 2. Draft the final answer from fragments. Include References from meta.references/doc_urls when available.
 3. MUST call finalize_answer with the same prompt + queryID before replying.
 4. Reply with: answer + finalize_answer follow-up text.
-5. After finalize_answer follow-up, check the next user reply before any normal response. If it means Yes/solved/thanks/OK, MUST call submit_feedback(resolved="1") before replying. If it means No/not solved/still not working, MUST call submit_feedback(resolved="0") before replying. Never say feedback was submitted unless submit_feedback was called.
+5. After finalize_answer follow-up, check the next user reply before any normal response. If it means Yes/已解决/thanks/OK, MUST call submit_feedback(resolved="1") before replying. If it means No/未解决/still not working, MUST call submit_feedback(resolved="0") before replying. Never say feedback was submitted unless submit_feedback was called.
 `.trim();
 export function createServer() {
     const server = new McpServer({
         name: "Tencent RTC MCP Server",
-        version: "1.6.1",
+        version: "1.6.5",
     }, {
         instructions: SERVER_INSTRUCTIONS,
     });

package/tools/common/finalize_answer.js

@@ -9,7 +9,7 @@ const registryFinalizeAnswerTool = (mcpServer) => {
             prompt: z.string().describe(parameter_descriptions.prompt),
             answer: z.string().describe(parameter_descriptions.answer),
             product: z.array(z.enum(['chat', 'call', 'live', 'room', 'push', 'rtcengine', 'native_trtc_sdk'])).min(1).max(4).optional().describe(parameter_descriptions.product),
-            framework: z.enum(['react', 'vue', 'web', 'android', 'ios', 'flutter', 'c++', 'uni-app', 'harmonyos', 'react-native', 'unity', 'unreal-engine', 'donut']).optional().describe(parameter_descriptions.framework),
+            framework: z.enum(['react', 'vue', 'web', 'miniprogram', 'android', 'ios', 'flutter', 'c++', 'uni-app', 'harmonyos', 'react-native', 'unity', 'unreal-engine', 'donut']).optional().describe(parameter_descriptions.framework),
             queryID: z.string().describe(parameter_descriptions.queryID),
         },
     }, (params) => {

package/tools/common/present_framework_choice.js

@@ -7,7 +7,7 @@ const PRODUCT_OPTIONS_MAP = {
     },
     call: {
         title: 'Supported Call / CallKit platforms or frameworks',
-        options: ['react', 'vue', 'flutter', 'android', 'ios', 'uni-app'],
+        options: ['web', 'miniprogram', 'react', 'vue', 'flutter', 'android', 'ios', 'uni-app'],
     },
     live: {
         title: 'Supported Live / LiveKit platforms or frameworks',
@@ -44,7 +44,7 @@ ${config.title}:
 ${options}
 
 After the user replies (hard rule — do not skip):
-- **Consultation / docs / API / component / feature lookup** → MUST call \`search_trtc_knowledge\` with **product + framework**
+- **Consultation / docs / API / component / feature lookup** → MUST call \`search_trtc_knowledge\` with **product + frameworks**
 - **Write integration code into a project** → MUST call the matching \`get_*_integration\` tool`;
 }
 const registryPresentFrameworkChoiceTool = (mcpServer) => {

package/tools/common/search_trtc_knowledge.js

@@ -10,7 +10,7 @@ const registrySearchTRTCKnowledgeTool = (mcpServer) => {
         inputSchema: {
             prompt: z.string().describe(parameter_descriptions.prompt),
             product: z.array(z.enum(['chat', 'call', 'live', 'room', 'push', 'rtcengine', 'native_trtc_sdk'])).min(1).max(4).optional().describe(parameter_descriptions.product),
-            framework: z.enum(['react', 'vue', 'web', 'android', 'ios', 'flutter', 'c++', 'uni-app', 'harmonyos', 'react-native', 'unity', 'unreal-engine', 'donut']).optional().describe(parameter_descriptions.framework),
+            frameworks: z.array(z.enum(['react', 'vue', 'web', 'miniprogram', 'android', 'ios', 'flutter', 'c++', 'uni-app', 'harmonyos', 'react-native', 'unity', 'unreal-engine', 'donut'])).min(1).optional().describe(parameter_descriptions.frameworks),
             queryID: z.string().describe(parameter_descriptions.queryID),
             ide: z.string().describe(parameter_descriptions.ide),
             types: z.array(z.enum([
@@ -26,14 +26,14 @@ const registrySearchTRTCKnowledgeTool = (mcpServer) => {
             method: 'search_trtc_knowledge',
             queryID: qid,
             prompt: params.prompt,
-            framework: params.framework ?? '',
+            framework: params.frameworks?.join(',') ?? '',
             product: params.product ? params.product.join(',') : '',
             ide: params.ide,
         });
         const response = searchKnowledge({
             prompt: params.prompt,
             product: params.product,
-            framework: params.framework,
+            frameworks: params.frameworks,
             types: params.types,
             scenario: params.scenario,
             limit: params.limit,

package/tools/common/submit_feedback.js

@@ -7,7 +7,7 @@ const registrySubmitFeedbackTool = (mcpServer) => {
         description,
         inputSchema: {
             prompt: z.string().describe(parameter_descriptions.prompt),
-            framework: z.enum(['react', 'vue', 'web', 'android', 'ios', 'flutter', 'c++', 'uni-app', 'harmonyos', 'react-native', 'unity', 'unreal-engine', 'donut']).optional().describe(parameter_descriptions.framework),
+            framework: z.enum(['react', 'vue', 'web', 'miniprogram', 'android', 'ios', 'flutter', 'c++', 'uni-app', 'harmonyos', 'react-native', 'unity', 'unreal-engine', 'donut']).optional().describe(parameter_descriptions.framework),
             queryID: z.string().describe(parameter_descriptions.queryID),
             resolved: z.enum(['0', '1']).describe(parameter_descriptions.resolved),
         },

package/tools/definitions/get_native_live_uikit_integration_def.js

@@ -0,0 +1,61 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
+const TOOL_DESCRIPTION = `
+Purpose:
+Return Native video live streaming integration docs based on TUILiveKit's preset UI components, for AI to complete out-of-the-box mobile (Android / iOS) video live streaming integration and code generation. Covers the live list page (audience entry), host streaming page, and audience watching page — all preset components with complete interactive UI and business logic (e.g. AnchorPrepareView, live list waterfall view, etc.).
+
+Typical use cases (shared trigger words, may also match the 'get_native_livekit_core_integration' Core tool):
+integrate LiveKit, TUILiveKit, video live streaming, live broadcast, host streaming, audience watching, live list, host page, watch page, live room list, Android, iOS
+When a shared trigger word is matched, **proactively ask the user first**: "Would you like to quickly integrate with the default live streaming UI (TUILiveKit preset), or build a custom UI on top of Core SDK / AtomicXCore?" Call this tool only after the user chooses "default/preset"; call 'get_native_livekit_core_integration' if they choose "custom/Core".
+
+Typical use cases (preset-only trigger words, match this tool exclusively, call directly without asking):
+TUILiveKit, Native TUILiveKit, Native Live UIKit, preset, preset integration, preset UI, preset host page, preset watch page, preset live list, default live streaming UI, out-of-the-box live streaming UI, ready-made streaming page, already have a live streaming UI, TUILiveKit Android, TUILiveKit iOS, AnchorPrepareView
+
+Input:
+- framework: android | ios
+- goals: feature module list (multi-select; results are organized in the order live_list → host_streaming → audience_streaming)
+- prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
+
+Returns:
+- content: [{ type: 'text', text: documentation body (common environment setup / dependency integration for all platforms, plus integration steps and code for the selected feature pages) }]
+
+Boundaries:
+- This tool is for **video live streaming (live)** scenarios only. Voice room (voice / audio room / seat) is **out of scope** — for that use 'get_native_livekit_core_integration' instead, or inform the user preset UI is not yet supported for voice room
+- framework only supports android | ios (TUILiveKit video live streaming preset UI has no flutter / uni-app docs yet — for that use 'get_native_livekit_core_integration' instead, or inform the user it is not supported)
+- If the user has not specified a platform, call 'present_framework_choice' first
+- If the user has explicitly indicated Core-specific trigger words such as "custom UI", "Core SDK", "AtomicXCore", "LiveCoreView", or "build my own live page", call 'get_native_livekit_core_integration' directly instead of this tool
+- Covers full page integration for host streaming / audience watching / live list only. Not responsible for co-guest, PK, gifts, barrage, beauty, or audio effects extensions (use 'search_trtc_knowledge' for those)
+${INTEGRATION_BOUNDARY_SUFFIX}
+`;
+const PARAMETER_DESCRIPTIONS = {
+    framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: android | ios.',
+    goals: 'Feature list (multi-select). Allowed values: live_list (live list page, audience entry) | host_streaming (host streaming page) | audience_streaming (audience watching page). A complete mobile live streaming app usually needs live_list + host_streaming + audience_streaming.',
+    prompt: "The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.",
+};
+export const GET_NATIVE_LIVE_UIKIT_INTEGRATION_DEFINITION = {
+    name: 'get_native_live_uikit_integration',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+// UI text shown to the AI (headings / sections / not-found hints).
+// The tool implementation (get_native_live_uikit_integration.ts) stays byte-identical between
+// zh/en and is auto-synced by sync-tools.js; this UI_TEXT block is the only per-locale text
+// that must be maintained separately for en.
+export const GET_NATIVE_LIVE_UIKIT_INTEGRATION_UI_TEXT = {
+    goalTitles: {
+        live_list: 'Live List Page (TUILiveKit Preset UI)',
+        host_streaming: 'Host Streaming Page (TUILiveKit Preset UI)',
+        audience_streaming: 'Audience Watching Page (TUILiveKit Preset UI)',
+    },
+    headerTitle: '# TUILiveKit Video Live Streaming (Native Preset UI) Integration Guide',
+    platformLabel: 'Platform',
+    selectedFeaturesLabel: 'Selected Features',
+    labelSeparator: ': ',
+    listSeparator: ', ',
+    headerNotes: [
+        'The environment setup and dependency integration steps common to all platforms are given below first, followed by the integration code for each selected feature page.',
+        'Strictly follow the class names, package names, and import paths in the documentation when generating code. Do not fabricate APIs.',
+    ],
+    prepareSectionTitle: (framework) => `Environment Setup and Code Integration (${framework} prerequisites)`,
+    prepareSectionFallback: '## Environment Setup and Code Integration\n\n> No preparation documentation found for this platform.',
+    goalNotFound: (framework) => `No integration documentation found for this feature on the ${framework} platform. Please confirm whether the goal and platform are supported, or use search_trtc_knowledge instead.`,
+};

package/tools/definitions/get_native_livekit_core_integration_def.js

@@ -4,11 +4,11 @@ Purpose:
 Return Native LiveKit Core base-integration docs based on AtomicXCore SDK for publishing, viewing, and room-list flows in live streaming or voice room apps.
 
 Typical use cases:
-Native LiveKit Core, AtomicXCore, no-UI SDK, core SDK, live streaming, voice room, publish, watch, room list, Android, iOS, Flutter, uni-app, live, voice, set up the base live flow, set up the base voice room flow
+Native LiveKit Core, AtomicXCore, no-UI SDK, core SDK, live streaming, voice room, publish, watch, room list, Android, iOS, Flutter, live, voice, set up the base live flow, set up the base voice room flow
 
 Input:
 - scenario: live | voice
-- framework: android | ios | flutter | uni-app
+- framework: android | ios | flutter
 - goals: feature module list
 - prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
@@ -23,7 +23,7 @@ ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
     scenario: 'Scenario type. Allowed values: live | voice. Use integration for publishing, viewing, or room list. Use search_trtc_knowledge for co-guest, PK, member list, beauty, audio effects, barrage, or gifts.',
-    framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: android | ios | flutter | uni-app.',
+    framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: android | ios | flutter.',
     goals: 'Feature list. Allowed values: host_streaming (host publish) | audience_streaming (audience watch) | live_list (room list).',
     prompt: "The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.",
 };

package/tools/definitions/present_framework_choice_def.js

@@ -3,7 +3,7 @@ Purpose:
 Guide the user to pick a supported platform or framework when the request does not clearly specify one, before continuing with search_trtc_knowledge or an integration tool.
 
 Typical use cases:
-platform choice, framework choice, pick a platform first, pick a framework first, platform not specified, framework not specified, integration guide, setup docs, quick start, API lookup, component lookup, feature lookup, how to configure, Chat UIKit integration, Call UIKit integration, Live UIKit integration, Room UIKit integration, CallKit API, LiveKit API, WebRTC SDK integration, Native TRTC SDK integration, react, vue, uni-app, flutter, android, ios, webrtc
+platform choice, framework choice, pick a platform first, pick a framework first, platform not specified, framework not specified, integration guide, setup docs, quick start, API lookup, component lookup, feature lookup, how to configure, Chat UIKit integration, Call UIKit integration, Live UIKit integration, Room UIKit integration, CallKit API, LiveKit API, WebRTC SDK integration, Native TRTC SDK integration, react, vue, web, miniprogram, uni-app, flutter, android, ios, webrtc
 
 Trigger examples:
 - Get the Chat UIKit integration guide (React/Vue not specified)
@@ -19,7 +19,7 @@ Returns:
 
 Boundaries:
 - This tool only collects the platform or framework choice. It does not return documentation content.
-- **Consultation chain (hard rule)**: API / component / feature / client troubleshooting / integration lookup without a platform -> MUST call this tool first, then search_trtc_knowledge with **product + framework**; do not skip.
+- **Consultation chain (hard rule)**: API / component / feature / client troubleshooting / integration lookup without a platform -> MUST call this tool first, then search_trtc_knowledge with **product + frameworks**; do not skip.
 - **Codegen chain (hard rule)**: user wants integration code in a project but platform is unclear -> MUST call this tool first, then the matching get_*_integration tool.
 - Cross-platform general questions (billing, server REST, UserSig principles) unrelated to a single client -> search_trtc_knowledge directly without this tool (product still MUST be inferred from the prompt).
 `;

package/tools/definitions/search_trtc_knowledge_def.js

@@ -5,9 +5,9 @@ For Tencent RTC documentation lookup (Chat / Call / Live / Room / Push / Web TRT
 push: TIMPush / push / vendor channel / FCM / Huawei / Xiaomi / OPPO (not chat) | chat: conversation / TUIKit / IM / theme
 call: CallKit | live: LiveKit | room: RoomKit / meeting | rtcengine: Web TRTC | native_trtc_sdk: TRTCCloud | cross-domain: ["push","chat"]
 
-**framework** (same decision order as requires-framework.ts):
+**frameworks** (same decision order as requires-framework.ts):
 If provided -> search. If response is needs_framework -> call present_framework_choice, then retry.
-chat + error code / ERR_ -> ask platform first | native_trtc_sdk -> MUST be android / ios / c++ | rtcengine -> implicit web
+chat + error code / ERR_ -> ask platform first | native_trtc_sdk -> MUST include one of android / ios / c++ | rtcengine -> implicit web
 push: vendor name alone is not a platform (framework optional); enablement / console / vendor config may omit framework; if android / ios / flutter etc. appear -> MUST pass framework
 billing / REST / Webhook / UserSig -> framework optional | if types only contain server_api / webhook / product -> framework optional
 console / product capability config (multi-device login, login policy, message storage, console settings) -> types=["product"], not feature; even if Agent passes feature, runtime treats as cross-platform product config
@@ -19,14 +19,14 @@ if types include api / component / feature / plugin / sdk / integration -> frame
 
 **L0/L1**: For local fragments, answer only from the returned text. For chat/urls/ results, fetch the official URL before stating facts. Never invent content.
 
-**Returns**: status, confidence, fragments(doc_urls), meta.references/exact_hits, top_score/second_score, queryID, message. Cite references/doc_urls only; never cite local fragment.source paths.
+**Returns**: status, confidence, fragments(doc_urls), meta.references/exact_hits, top_score/second_score, queryID, message, meta.answer_contract. The answer MUST strictly follow answer_contract (conclusion first, user-actionable, make unconfirmed points explicit); do not spell out the evidence chain in the body, and never output system jargon such as "matched fragments / search results / confidence", but keep a "References" section at the end listing references/doc_urls.
 
 **Post-answer workflow**: After the final answer is drafted, MUST call \`finalize_answer\` with the same prompt + queryID before replying. Append its follow-up text. On explicit follow-up feedback, call \`submit_feedback\`.
 `;
 const PARAMETER_DESCRIPTIONS = {
     prompt: "The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.",
-    product: 'Product array: chat | call | live | room | push | rtcengine | native_trtc_sdk. If inferable, MUST pass it. Push takes priority for TIMPush / push topics and must not be misrouted to chat. If uncertain, ask the user first.',
-    framework: 'Platform: react | vue | web | android | ios | flutter | c++ | uni-app | harmonyos | react-native | unity | unreal-engine | donut. Follow the decision table in the tool description. harmonyos / react-native / unity / unreal-engine / donut are only valid for push.',
+    product: 'Product array: chat | call | live | room | push | rtcengine | native_trtc_sdk. If inferable, MUST pass it. Push takes priority for TIMPush / push topics and must not be misrouted to chat. Common live keywords: LiveKit / live streaming / voice room / TUILiveKit / AtomicXCore / host streaming / watch live. If uncertain, ask the user first.',
+    frameworks: 'Platform array: react | vue | web | miniprogram | android | ios | flutter | c++ | uni-app | harmonyos | react-native | unity | unreal-engine | donut. Multiple platforms can be passed for cross-platform lookup. For CallKit, TUICallKit is best searched separately by react/vue, while TUICallEngine/TUICallEvent still map to web; use miniprogram for Mini Program. harmonyos / react-native / unity / unreal-engine / donut are only valid for push.',
     types: 'Usually omit. Allowed values: integration | component | feature | api | plugin | sdk | faq | error_code | product | server_api | webhook. component and feature are equivalent (match both). Discovery/listing questions ("what components are available") MUST omit types. Console/billing/product-capability config -> product (not feature). Do not proactively over-narrow.',
     scenario: 'live | voice. Only valid for the live product.',
     queryID: "First call: ''. Follow-up calls in the same consultation MUST pass through the original queryID returned by the server.",

package/tools/index.js

@@ -14,6 +14,7 @@ import { registryGetNativeCallKitCoreIntegrationTool } from './call/get_native_c
 // live
 import { registryGetWebLiveUIKitIntegrationTool } from './live/get_web_live_uikit_integration.js';
 import { registryGetNativeLiveKitCoreIntegrationTool } from './live/get_native_livekit_core_integration.js';
+import { registryGetNativeLiveUIKitIntegrationTool } from './live/get_native_live_uikit_integration.js';
 // room
 import { registryGetWebRoomUIKitIntegrationTool } from './room/get_web_room_uikit_integration.js';
 import { registryGetWebRoomCoreIntegrationTool } from './room/get_web_room_core_integration.js';
@@ -33,6 +34,7 @@ function registryTools(mcpServer) {
     // live
     registryGetWebLiveUIKitIntegrationTool(mcpServer);
     registryGetNativeLiveKitCoreIntegrationTool(mcpServer);
+    registryGetNativeLiveUIKitIntegrationTool(mcpServer);
     // room
     registryGetWebRoomUIKitIntegrationTool(mcpServer);
     registryGetWebRoomCoreIntegrationTool(mcpServer);

package/tools/live/get_native_live_uikit_integration.js

@@ -0,0 +1,69 @@
+import { z } from 'zod';
+import { GET_NATIVE_LIVE_UIKIT_INTEGRATION_DEFINITION, GET_NATIVE_LIVE_UIKIT_INTEGRATION_UI_TEXT as UI_TEXT, } from '../definitions/get_native_live_uikit_integration_def.js';
+import { getIntegrationContent } from '../../utils/get-doc-content.js';
+import { reportCLSClient } from '../../utils/report-cls-client.js';
+// goal → 直播列表/开播/观看对应的 preset 文档文件名（均在 livekit/preset/live/{framework}/ 下）
+// 展示文案（title）统一从 UI_TEXT.goalTitles 取，做到 zh/en 按 locale 差异化。
+const GOAL_FILE = {
+    host_streaming: 'live-host-integration.md',
+    audience_streaming: 'live-audience-integration.md',
+    live_list: 'live-list-integration.md',
+};
+// 观众进直播间需要先有列表入口；固定的推荐阅读顺序，保证多 goal 时输出结构稳定
+const GOAL_ORDER = ['live_list', 'host_streaming', 'audience_streaming'];
+const DOC_NOT_FOUND = 'Not found relevant documents';
+function getResultText(params) {
+    const { framework = '', goals = [], prompt = '' } = params;
+    // 去重 + 稳定排序，避免同一 goal 传多次导致重复正文
+    const uniqueGoals = GOAL_ORDER.filter((goal) => goals.includes(goal));
+    reportCLSClient({
+        method: 'get_native_live_uikit_integration',
+        prompt,
+        framework,
+        info: `live:${uniqueGoals.join(',')}`,
+    });
+    const prepareContent = getIntegrationContent(['livekit', 'preset', 'live', framework, 'prepare-integration.md']);
+    const sections = uniqueGoals.map((goal) => {
+        const title = UI_TEXT.goalTitles[goal];
+        const file = GOAL_FILE[goal];
+        const content = getIntegrationContent(['livekit', 'preset', 'live', framework, file]);
+        if (!content || content === DOC_NOT_FOUND) {
+            return `## ${title}\n\n> ${UI_TEXT.goalNotFound(framework)}`;
+        }
+        return `## ${title}\n\n${content}`;
+    });
+    const header = [
+        UI_TEXT.headerTitle,
+        `- ${UI_TEXT.platformLabel}${UI_TEXT.labelSeparator}${framework}`,
+        `- ${UI_TEXT.selectedFeaturesLabel}${UI_TEXT.labelSeparator}${uniqueGoals.map((g) => UI_TEXT.goalTitles[g]).join(UI_TEXT.listSeparator)}`,
+        ...UI_TEXT.headerNotes.map((note) => `- ${note}`),
+    ].join('\n');
+    const prepareSection = (!prepareContent || prepareContent === DOC_NOT_FOUND)
+        ? UI_TEXT.prepareSectionFallback
+        : `## ${UI_TEXT.prepareSectionTitle(framework)}\n\n${prepareContent}`;
+    return [header, prepareSection, '---', ...sections].join('\n\n');
+}
+const registryGetNativeLiveUIKitIntegrationTool = (mcpServer) => {
+    const { name, description, parameter_descriptions } = GET_NATIVE_LIVE_UIKIT_INTEGRATION_DEFINITION;
+    mcpServer.registerTool(name, {
+        description,
+        inputSchema: {
+            framework: z.enum(['android', 'ios']).describe(parameter_descriptions.framework),
+            goals: z
+                .array(z.enum(['live_list', 'host_streaming', 'audience_streaming']))
+                .min(1)
+                .describe(parameter_descriptions.goals),
+            prompt: z.string().describe(parameter_descriptions.prompt),
+        },
+    }, (params) => {
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: getResultText(params),
+                },
+            ],
+        };
+    });
+};
+export { registryGetNativeLiveUIKitIntegrationTool };

package/tools/live/get_native_livekit_core_integration.js

@@ -5,15 +5,15 @@ import { reportCLSClient } from '../../utils/report-cls-client.js';
 function generatePathMap(scenario, framework) {
     if (scenario === 'live') {
         return {
-            'host_streaming': ['livekit', 'core-sdk', 'live', `${framework}`, 'live-integration.md'],
-            'audience_streaming': ['livekit', 'core-sdk', 'live', `${framework}`, 'live-integration.md'],
-            'live_list': ['livekit', 'core-sdk', 'live', `${framework}`, 'live-live-list.md']
+            'host_streaming': ['livekit', 'core-sdk', 'live', `${framework}`, 'integration.md'],
+            'audience_streaming': ['livekit', 'core-sdk', 'live', `${framework}`, 'integration.md'],
+            'live_list': ['livekit', 'core-sdk', 'features', `${framework}`, 'live-list.md']
         };
     }
     return {
-        'host_streaming': ['livekit', 'core-sdk', 'voice', `${framework}`, 'voice-integration.md'],
-        'audience_streaming': ['livekit', 'core-sdk', 'voice', `${framework}`, 'voice-integration.md'],
-        'live_list': ['livekit', 'core-sdk', 'voice', `${framework}`, 'voice-room-list.md']
+        'host_streaming': ['livekit', 'core-sdk', 'voice', `${framework}`, 'integration.md'],
+        'audience_streaming': ['livekit', 'core-sdk', 'voice', `${framework}`, 'integration.md'],
+        'live_list': ['livekit', 'core-sdk', 'features', `${framework}`, 'live-list.md']
     };
 }
 async function getResultText(params) {

package/utils/report-cls-client.js

@@ -28,7 +28,7 @@ function sendCLSReport(reportData) {
     const time = Date.now();
     const data = {
         platform: 'mcp',
-        verison: '1.6.4',
+        verison: '1.6.5',
         sdkappid: `${SDKAppID}`,
         method: method,
         userid: queryID || userID,

package/utils/report-es-client.js

@@ -7,7 +7,7 @@ function reportESClient(reportData) {
         report: [
             {
                 platform: 'mcp',
-                version: '1.6.4',
+                version: '1.6.5',
                 sdkappid: `${SDKAppID}`,
                 method: method,
                 userID: `${userID}`,

package/resource/knowledge/callkit/preset/web/api.md

@@ -1,83 +0,0 @@
-## TUICallKit (Includes UI Components)
-
-TUICallKit is an audio and video call component that **includes a UI component**. You can quickly implement a WhatsApp-like audio and video calling scenario with this component.
-
-|API|Description|
-|---------|---------|
-|[init](https://www.tencentcloud.com/document/product/647/51015#init)|Initialize TUICallKit.|
-|[calls](https://www.tencentcloud.com/document/product/647/51015#calls)|Initiate a one-to-one or multi-person call.|
-|[join](https://www.tencentcloud.com/document/product/647/51015#join)|Proactively join a call.|
-|[setCallingBell](https://www.tencentcloud.com/document/product/647/51015#setCallingBell)|Customize user's ringtone.|
-|[setSelfInfo](https://www.tencentcloud.com/document/product/647/51015#setSelfInfo)|Set your own nickname and avatar.|
-|[enableMuteMode](https://www.tencentcloud.com/document/product/647/51015#enableMuteMode)|Turn on/off ringtone.|
-|[enableFloatWindow](https://www.tencentcloud.com/document/product/647/51015#enableFloatWindow)|Turn on/off the floating window function.|
-|[enableVirtualBackground](https://www.tencentcloud.com/document/product/647/51015#enableVirtualBackground)|Turn on/off the blurred background function button.|
-|[setLanguage](https://www.tencentcloud.com/document/product/647/51015#setLanguage)|Set the call language for the TUICallKit component.|
-|[hideFeatureButton](https://www.tencentcloud.com/document/product/647/51015#hideFeatureButton)|Hidden Button.|
-|[setLocalViewBackgroundImage](https://www.tencentcloud.com/document/product/647/51015#setLocalViewBackgroundImage)|Set the background image for the local user's call interface.|
-|[setRemoteViewBackgroundImage](https://www.tencentcloud.com/document/product/647/51015#setRemoteViewBackgroundImage)|Set the background image for the remote user's call interface.|
-|[setLayoutMode](https://www.tencentcloud.com/document/product/647/51015#setLayoutMode)|Set the call interface layout mode.|
-|[setCameraDefaultState](https://www.tencentcloud.com/document/product/647/51015#setCameraDefaultState)|Set whether the camera is opened by default.|
-|[destroyed](https://www.tencentcloud.com/document/product/647/51015#destroyed)|Destroy TUICallKit.|
-|[getTUICallEngineInstance](https://www.tencentcloud.com/document/product/647/51015#getTUICallEngineInstance)|Get TUICallEngine instance.|
-
-## TUICallEngine (No UI)
-
-TUICallEngine API is an audio and video call component that **offers a No UI interface**. You can use this set of APIs to custom encapsulate according to your business needs.
-
-|API|Description|
-|---------|---------|
-|[createInstance](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#.createInstance)|Creating a TUICallEngine Instance (Singleton Pattern)|
-|[destroyInstance](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#destroyInstance)|Terminating a TUICallEngine Instance (Singleton Pattern)|
-|[on](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#on)|Listening on events|
-|[off](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#off)|Canceling Event Listening|
-|[login](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#login)|Sign in Interface|
-|[logout](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#logout)|Logout Interface|
-|[setSelfInfo](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setSelfInfo)|Configure the user's nickname and profile photo|
-|[calls](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#calls)|Initiate a one-on-one call|
-|[join](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#join)|Proactively join a call.|
-|[accept](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#accept)|Answer Calls|
-|[reject](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#reject)|Decline Call|
-|[hangup](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#hangup)|End Calls|
-|[startRemoteView](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#startRemoteView)|Initiate Remote Screen Rendering|
-|[stopRemoteView](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#stopRemoteView)|Stop Remote Screen Rendering|
-|[openCamera](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#openCamera)|Enable the camera|
-|[closeCamera](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#closeCamera)|Turn Off Camera|
-|[switchCamera](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#switchCamera)|Switch between front and rear cameras, note: only supported on mobile devices.|
-|[openMicrophone](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#openMicrophone)|Enable Microphone|
-|[closeMicrophone](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#closeMicrophone)|Turn off the microphone|
-|[setVideoQuality](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setVideoQuality)|Set video quality|
-|[getDeviceList](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#getDeviceList)|Access device list|
-|[switchDevice](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#switchDevice)|Switch camera or microphone devices|
-|[enableMultiDeviceAbility](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#enableMultiDeviceAbility)|Turn on/off the multi-device login mode of TUICallEngine.|
-|[setBlurBackground](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setBlurBackground)|Switch/set background blur|
-|[setVirtualBackground](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setVirtualBackground)|Switch/set image background blur|
-
-## Event Types
-
-TUICallEvent is the callback event class corresponding to TUICallEngine. Through this callback, you can listen to the callback events of interest.
-
-|EVENT|Description|
-|---------|---------|
-|[TUICallEvent.ERROR](https://www.tencentcloud.com/document/product/647/51017#error)|An error occurred during the call.|
-|[TUICallEvent.KICKED_OUT](https://www.tencentcloud.com/document/product/647/51017#kicked_out)|Receiving this event after a duplicate sign-in indicates that the user has been removed from the room|
-|[TUICallEvent.USER_ACCEPT](https://www.tencentcloud.com/document/product/647/51017#user_accept)|If a user answers, this event will be received.** v4.x.x is deprecated**|
-|[TUICallEvent.USER_ENTER](https://www.tencentcloud.com/document/product/647/51017#user_enter)|A user joined the call.|
-|[TUICallEvent.USER_LEAVE](https://www.tencentcloud.com/document/product/647/51017#user_leave)|A user left the call.|
-|[TUICallEvent.REJECT](https://www.tencentcloud.com/document/product/647/51017#reject)|A user declined the call.|
-|[TUICallEvent.NO_RESP](https://www.tencentcloud.com/document/product/647/51017#no_resp)|A user didn't respond.|
-|[TUICallEvent.LINE_BUSY](https://www.tencentcloud.com/document/product/647/51017#line_busy)|A user was busy.|
-|[TUICallEvent.USER_VIDEO_AVAILABLE](https://www.tencentcloud.com/document/product/647/51017#user_video_available)|Whether a user has a video stream.|
-|[TUICallEvent.USER_AUDIO_AVAILABLE](https://www.tencentcloud.com/document/product/647/51017#user_audio_available)|Whether a user has an audio stream.|
-|[TUICallEvent.USER_VOICE_VOLUME](https://www.tencentcloud.com/document/product/647/51017#user_voice_volume)|The volume levels of all users.|
-|TUICallEvent.ON_CALL_BEGIN|Call connected event|
-|TUICallEvent.ON_CALL_RECEIVED|Call request event|
-|TUICallEvent.ON_CALL_CONNECTED|Call not connected event|
-|TUICallEvent.ON_CALL_END|The call ended.|
-|[TUICallEvent.DEVICED_UPDATED](https://www.tencentcloud.com/document/product/647/51017#deviced_updated)|Device list update, this event will be received|
-|TUICallEvent.ON_USER_NETWORK_QUALITY_CHANGED|All user network quality events|
-
-## Document Link
-- [TUICallEngine](https://www.tencentcloud.com/document/product/647/51016)
-
-- [TUICallEvent](https://www.tencentcloud.com/document/product/647/51017)