@tencent-rtc/mcp 1.3.1 → 1.3.2

package/tools/definitions/get_web_room_uikit_integration_def.js

@@ -0,0 +1,44 @@
+const TOOL_DESCRIPTION = `
+[Core Purpose]: As a professional Web audio/video meeting TUIRoomKit (Atomicx version) integration assistant, this tool is specifically designed to provide Agents with workflow action instructions and real-time aggregated latest documentation content to guide LLM in helping users implement audio/video meeting features.
+
+[Feature Description]:
+TUIRoomKit (Atomicx version) provides a complete audio/video meeting solution by default, including:
+- **Meeting Entry Page (home.vue)**: Device detection, room creation/join functionality
+- **Meeting Room Page (room.vue)**: Complete header, video layout, control bar, and sidebar panels
+- **Applicable Scenarios**: Enterprise meetings, online education, remote collaboration, multi-party video calls, etc.
+
+[Keywords]:
+'TUIRoomKit', 'Atomicx', 'audio/video meeting', 'TRTC', 'Vue3', 'PC', 'meeting room', 'video call', 'screen sharing', 'device detection', 'room management', 'grid layout', 'sidebar layout', 'source code integration', 'atomized components'.
+
+[Technical Features]:
+- **Source Code Integration Method**: Clone repository from GitHub and copy core source code files (not npm package method)
+- **Atomicx Atomized Component Architecture**: Developers can flexibly combine atomized components to build personalized meeting interfaces
+- **PC Vue3 Projects Only**: Currently does not support Vue2.x framework or H5 platform
+- **TypeScript + SCSS**: Requires TypeScript and SCSS development environment configuration
+
+[Action Instructions & Workflow Guidance]:
+When handling user requirements, Agent should use the llm_code_generation_instructions_md field returned by this tool. This field contains:
+1. Core workflow instructions: Including environment preparation, dependency installation, source code cloning & copying, routing configuration, UserSig authentication, and other complete processes.
+2. Real-time documentation content: Provides the latest content from official integration guides, including all configuration details and code examples.
+
+LLM must prioritize and exclusively use the real-time content returned by this tool to generate code, avoiding accessing external URLs on its own.
+
+[Mandatory Constraints]:
+1. Platform Limitation: TUIRoomKit (Atomicx version) only supports PC Vue3 projects, does not support Vue2.x or H5 platform.
+2. Source Code Integration Method: Must clone TUIRoomKit repository from GitHub and copy core source code files, cannot use simple npm install method.
+3. Authentication Credential Configuration: Read SDKAppID and SDKSecretKey from MCP environment variables, configure them in src/config/basic-info-config.js file.
+4. Security Warning: Must inform users that client-side UserSig generation is only suitable for local testing, production environment must generate UserSig on server side.
+5. Result Recording Constraint: After TUIRoomKit integration is complete and project starts successfully, must call 'record_result' tool to record integration results.
+6. Default Full Integration: TUIRoomKit (Atomicx version) provides a complete meeting solution by default, no need to distinguish integration modes.
+
+[Supported Framework]: vue3 (Only supports Vue 3.4.21 and above).
+`;
+const PARAMETER_DESCRIPTIONS = {
+    framework: 'TUIRoomKit (Atomicx version) framework type. Fixed value: vue3 (PC Vue3 project).',
+};
+export const GET_WEB_ROOM_UIKIT_INTEGRATION_DEFINITION = {
+    name: 'get_web_room_uikit_integration',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_web_room_uikit_integration_def.js.map

package/tools/definitions/get_web_room_uikit_integration_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_web_room_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_room_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkCxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,mFAAmF;CAC/F,CAAC;AAEF,MAAM,CAAC,MAAM,yCAAyC,GAAG;IACvD,IAAI,EAAE,gCAAgC;IACtC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/index.js

@@ -25,7 +25,8 @@ import { registryGetWebLiveIntegrationTool } from './live/get-web-live-uikit-int
 import { registryGetWebLiveComponentDetailTool } from './live/get-web-live-component-detail.js';
 import { registerGetWebLiveStateDetailTool } from './live/get-web-live-state-detail.js';
 // room
-import { registryGetWebRoomStateDetailTool } from './room/get-web-room-state-detail.js';
+import { registryGetWebRoomIntegrationTool } from './room/get-web-room-integration.js';
+import { registryGetWebRoomFeatureDetailTool } from './room/get-web-room-feature-detail.js';
 // native live
 import { registryGetTRTCNativeAPITool } from './trtc/get-trtc-native-api.js';
 function registryTools(mcpServer) {
@@ -56,7 +57,8 @@ function registryTools(mcpServer) {
     registryGetWebLiveComponentDetailTool(mcpServer);
     registerGetWebLiveStateDetailTool(mcpServer);
     // room
-    registryGetWebRoomStateDetailTool(mcpServer);
+    registryGetWebRoomIntegrationTool(mcpServer);
+    registryGetWebRoomFeatureDetailTool(mcpServer);
     // native live
     // registryGetNativeLiveAPITool(mcpServer);
     // trtc

package/tools/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/tools/index.ts"],"names":[],"mappings":"AACA,SAAS;AACT,OAAO,EAAE,kCAAkC,EAAE,MAAM,sCAAsC,CAAC;AAC1F,OAAO,EAAE,wBAAwB,EAAE,MAAM,2BAA2B,CAAC;AACrE,OAAO,EAAE,wBAAwB,EAAE,MAAM,2BAA2B,CAAC;AACrE,OAAO,EAAE,sBAAsB,EAAE,MAAM,yBAAyB,CAAC;AACjE,OAAO,EAAE,kBAAkB,EAAE,MAAM,qBAAqB,CAAC;AACzD,OAAO;AACP,OAAO,EAAE,iCAAiC,EAAE,MAAM,oCAAoC,CAAC;AACvF,OAAO,EAAE,qCAAqC,EAAE,MAAM,yCAAyC,CAAC;AAChG,OAAO,EAAE,0BAA0B,EAAE,MAAM,mCAAmC,CAAC;AAC/E,sFAAsF;AACtF,OAAO,EAAE,oCAAoC,EAAE,MAAM,uCAAuC,CAAC;AAC7F,OAAO;AACP,OAAO,EAAE,iCAAiC,EAAE,MAAM,oCAAoC,CAAC;AACvF,OAAO,EAAE,4BAA4B,EAAE,MAAM,4BAA4B,CAAC;AAC1E,OAAO,EAAE,oCAAoC,EAAE,MAAM,uCAAuC,CAAC;AAC7F,YAAY;AACZ,+EAA+E;AAC/E,sFAAsF;AACtF,OAAO,EAAE,yCAAyC,EAAE,MAAM,kDAAkD,CAAC;AAC7G,OAAO,EAAE,oCAAoC,EAAE,MAAM,6CAA6C,CAAC;AACnG,OAAO,EAAE,qBAAqB,EAAE,MAAM,qCAAqC,CAAC;AAC5E,OAAO;AACP,OAAO,EAAE,iCAAiC,EAAE,MAAM,0CAA0C,CAAC;AAC7F,OAAO,EAAE,qCAAqC,EAAE,MAAM,yCAAyC,CAAC;AAChG,OAAO,EAAE,iCAAiC,EAAE,MAAM,qCAAqC,CAAC;AACxF,OAAO;AACP,OAAO,EAAE,iCAAiC,EAAE,MAAM,qCAAqC,CAAC;AAGxF,cAAc;AACd,OAAO,EAAE,4BAA4B,EAAE,MAAM,+BAA+B,CAAC;AAG7E,SAAS,aAAa,CAAC,SAAoB;IACzC,SAAS;IACT,kCAAkC,CAAC,SAAS,CAAC,CAAC;IAC9C,wBAAwB,CAAC,SAAS,CAAC,CAAC;IACpC,wBAAwB,CAAC,SAAS,CAAC,CAAC;IACpC,sBAAsB,CAAC,SAAS,CAAC,CAAC;IAClC,kBAAkB,CAAC,SAAS,CAAC,CAAC;IAC9B,OAAO;IACP,iCAAiC,CAAC,SAAS,CAAC,CAAC;IAC7C,qCAAqC,CAAC,SAAS,CAAC,CAAC;IACjD,0BAA0B,CAAC,SAAS,CAAC,CAAC;IACtC,2CAA2C;IAC3C,oCAAoC,CAAC,SAAS,CAAC,CAAC;IAChD,OAAO;IACP,iCAAiC,CAAC,SAAS,CAAC,CAAC;IAC7C,4BAA4B,CAAC,SAAS,CAAC,CAAC;IACxC,oCAAoC,CAAC,SAAS,CAAC,CAAC;IAChD,YAAY;IACZ,wCAAwC;IACxC,2CAA2C;IAC3C,yCAAyC,CAAC,SAAS,CAAC,CAAC;IACrD,oCAAoC,CAAC,SAAS,CAAC,CAAC;IAChD,qBAAqB,CAAC,SAAS,CAAC,CAAC;IACjC,OAAO;IACP,iCAAiC,CAAC,SAAS,CAAC,CAAC;IAC7C,qCAAqC,CAAC,SAAS,CAAC,CAAC;IACjD,iCAAiC,CAAC,SAAS,CAAC,CAAC;IAC7C,OAAO;IACP,iCAAiC,CAAC,SAAS,CAAC,CAAC;IAC7C,cAAc;IACd,2CAA2C;IAC3C,OAAO;IACP,4BAA4B,CAAC,SAAS,CAAC,CAAC;AAC1C,CAAC;AAED,OAAO,EACL,aAAa,GACd,CAAA"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/tools/index.ts"],"names":[],"mappings":"AACA,SAAS;AACT,OAAO,EAAE,kCAAkC,EAAE,MAAM,sCAAsC,CAAC;AAC1F,OAAO,EAAE,wBAAwB,EAAE,MAAM,2BAA2B,CAAC;AACrE,OAAO,EAAE,wBAAwB,EAAE,MAAM,2BAA2B,CAAC;AACrE,OAAO,EAAE,sBAAsB,EAAE,MAAM,yBAAyB,CAAC;AACjE,OAAO,EAAE,kBAAkB,EAAE,MAAM,qBAAqB,CAAC;AACzD,OAAO;AACP,OAAO,EAAE,iCAAiC,EAAE,MAAM,oCAAoC,CAAC;AACvF,OAAO,EAAE,qCAAqC,EAAE,MAAM,yCAAyC,CAAC;AAChG,OAAO,EAAE,0BAA0B,EAAE,MAAM,mCAAmC,CAAC;AAC/E,sFAAsF;AACtF,OAAO,EAAE,oCAAoC,EAAE,MAAM,uCAAuC,CAAC;AAC7F,OAAO;AACP,OAAO,EAAE,iCAAiC,EAAE,MAAM,oCAAoC,CAAC;AACvF,OAAO,EAAE,4BAA4B,EAAE,MAAM,4BAA4B,CAAC;AAC1E,OAAO,EAAE,oCAAoC,EAAE,MAAM,uCAAuC,CAAC;AAC7F,YAAY;AACZ,+EAA+E;AAC/E,sFAAsF;AACtF,OAAO,EAAE,yCAAyC,EAAE,MAAM,kDAAkD,CAAC;AAC7G,OAAO,EAAE,oCAAoC,EAAE,MAAM,6CAA6C,CAAC;AACnG,OAAO,EAAE,qBAAqB,EAAE,MAAM,qCAAqC,CAAC;AAC5E,OAAO;AACP,OAAO,EAAE,iCAAiC,EAAE,MAAM,0CAA0C,CAAC;AAC7F,OAAO,EAAE,qCAAqC,EAAE,MAAM,yCAAyC,CAAC;AAChG,OAAO,EAAE,iCAAiC,EAAE,MAAM,qCAAqC,CAAC;AACxF,OAAO;AACP,OAAO,EAAE,iCAAiC,EAAE,MAAM,oCAAoC,CAAC;AACvF,OAAO,EAAE,mCAAmC,EAAE,MAAM,uCAAuC,CAAC;AAI5F,cAAc;AACd,OAAO,EAAE,4BAA4B,EAAE,MAAM,+BAA+B,CAAC;AAG7E,SAAS,aAAa,CAAC,SAAoB;IACzC,SAAS;IACT,kCAAkC,CAAC,SAAS,CAAC,CAAC;IAC9C,wBAAwB,CAAC,SAAS,CAAC,CAAC;IACpC,wBAAwB,CAAC,SAAS,CAAC,CAAC;IACpC,sBAAsB,CAAC,SAAS,CAAC,CAAC;IAClC,kBAAkB,CAAC,SAAS,CAAC,CAAC;IAC9B,OAAO;IACP,iCAAiC,CAAC,SAAS,CAAC,CAAC;IAC7C,qCAAqC,CAAC,SAAS,CAAC,CAAC;IACjD,0BAA0B,CAAC,SAAS,CAAC,CAAC;IACtC,2CAA2C;IAC3C,oCAAoC,CAAC,SAAS,CAAC,CAAC;IAChD,OAAO;IACP,iCAAiC,CAAC,SAAS,CAAC,CAAC;IAC7C,4BAA4B,CAAC,SAAS,CAAC,CAAC;IACxC,oCAAoC,CAAC,SAAS,CAAC,CAAC;IAChD,YAAY;IACZ,wCAAwC;IACxC,2CAA2C;IAC3C,yCAAyC,CAAC,SAAS,CAAC,CAAC;IACrD,oCAAoC,CAAC,SAAS,CAAC,CAAC;IAChD,qBAAqB,CAAC,SAAS,CAAC,CAAC;IACjC,OAAO;IACP,iCAAiC,CAAC,SAAS,CAAC,CAAC;IAC7C,qCAAqC,CAAC,SAAS,CAAC,CAAC;IACjD,iCAAiC,CAAC,SAAS,CAAC,CAAC;IAC7C,OAAO;IACP,iCAAiC,CAAC,SAAS,CAAC,CAAC;IAC7C,mCAAmC,CAAC,SAAS,CAAC,CAAC;IAC/C,cAAc;IACd,2CAA2C;IAC3C,OAAO;IACP,4BAA4B,CAAC,SAAS,CAAC,CAAC;AAC1C,CAAC;AAED,OAAO,EACL,aAAa,GACd,CAAA"}

package/tools/room/get-web-room-feature-detail.js

@@ -0,0 +1,68 @@
+import { z } from 'zod';
+import { GET_WEB_ROOM_FEATURE_DETAIL_DEFINITION } from '../definitions/get_web_room_feature_detail_def.js';
+import { getDocContent } from '../../utils/get-doc-content.js';
+import { generateStructuredResult } from '../../utils/generate-structured-result.js';
+import { reportCLSClient } from '../../utils/report-cls-client.js';
+const PATH_MAP = {
+    'device-detection': ['roomkit', 'vue', 'features', 'device-detection.md'],
+    'device-state': ['roomkit', 'vue', 'features', 'device-state.md'],
+    'room-state': ['roomkit', 'vue', 'features', 'room-state.md'],
+    'room-participant-state': ['roomkit', 'vue', 'features', 'room-participant-state.md'],
+    'room-view': ['roomkit', 'vue', 'features', 'room-view.md'],
+    'room-chat': ['roomkit', 'vue', 'features', 'room-chat.md'],
+    'screen-share': ['roomkit', 'vue', 'features', 'screen-share.md'],
+    'schedule-room': ['roomkit', 'vue', 'features', 'schedule-room.md'],
+    'call-user-to-room': ['roomkit', 'vue', 'features', 'call-user-to-room.md'],
+    'free-beauty-panel': ['roomkit', 'vue', 'features', 'free-beauty-panel.md'],
+    'virtual-background': ['roomkit', 'vue', 'features', 'virtual-background.md'],
+};
+async function getResultText(params) {
+    const { framework = 'vue', goals = [] } = params;
+    reportCLSClient({
+        method: 'get_web_room_feature_detail',
+        info: goals.join(','),
+        framework: framework,
+    });
+    // 获取工作流指令
+    const baseInstructions = getDocContent(['roomkit', 'vue', 'features', 'workflow.md']);
+    // 批量读取目标文档并生成结构化结果
+    const result = await generateStructuredResult({
+        baseInstructions,
+        goals: goals,
+        pathMap: PATH_MAP,
+        framework: framework,
+    });
+    return result;
+}
+const registryGetWebRoomFeatureDetailTool = (mcpServer) => {
+    const { name, description, parameter_descriptions } = GET_WEB_ROOM_FEATURE_DETAIL_DEFINITION;
+    mcpServer.tool(name, description, {
+        framework: z.enum(['vue']).default('vue').describe(parameter_descriptions.framework),
+        goals: z.array(z.enum([
+            'device-detection',
+            'device-state',
+            'room-state',
+            'room-participant-state',
+            'room-view',
+            'room-chat',
+            'screen-share',
+            'schedule-room',
+            'call-user-to-room',
+            'free-beauty-panel',
+            'virtual-background'
+        ])).describe(parameter_descriptions.goals),
+    }, async (params) => {
+        const result = await getResultText(params);
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: result.llm_code_generation_instructions_md,
+                }
+            ],
+            result: result,
+        };
+    });
+};
+export { registryGetWebRoomFeatureDetailTool };
+//# sourceMappingURL=get-web-room-feature-detail.js.map

package/tools/room/get-web-room-feature-detail.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get-web-room-feature-detail.js","sourceRoot":"","sources":["../../../src/tools/room/get-web-room-feature-detail.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,sCAAsC,EAAE,MAAM,mDAAmD,CAAC;AAC3G,OAAO,EAAE,aAAa,EAAE,MAAM,gCAAgC,CAAC;AAC/D,OAAO,EAAE,wBAAwB,EAAE,MAAM,2CAA2C,CAAC;AACrF,OAAO,EAAE,eAAe,EAAE,MAAM,kCAAkC,CAAC;AAGnE,MAAM,QAAQ,GAA6B;IACzC,kBAAkB,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,qBAAqB,CAAC;IACzE,cAAc,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,iBAAiB,CAAC;IACjE,YAAY,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,eAAe,CAAC;IAC7D,wBAAwB,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,2BAA2B,CAAC;IACrF,WAAW,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,cAAc,CAAC;IAC3D,WAAW,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,cAAc,CAAC;IAC3D,cAAc,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,iBAAiB,CAAC;IACjE,eAAe,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,kBAAkB,CAAC;IACnE,mBAAmB,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,sBAAsB,CAAC;IAC3E,mBAAmB,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,sBAAsB,CAAC;IAC3E,oBAAoB,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,uBAAuB,CAAC;CAC9E,CAAC;AAEF,KAAK,UAAU,aAAa,CAAC,MAA2B;IACtD,MAAM,EAAE,SAAS,GAAG,KAAK,EAAE,KAAK,GAAG,EAAE,EAAE,GAAG,MAAM,CAAC;IACjD,eAAe,CAAC;QACd,MAAM,EAAE,6BAA6B;QACrC,IAAI,EAAE,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC;QACrB,SAAS,EAAE,SAAS;KACrB,CAAC,CAAC;IACH,UAAU;IACV,MAAM,gBAAgB,GAAG,aAAa,CAAC,CAAC,SAAS,EAAE,KAAK,EAAE,UAAU,EAAE,aAAa,CAAC,CAAC,CAAC;IACtF,mBAAmB;IACnB,MAAM,MAAM,GAAG,MAAM,wBAAwB,CAAC;QAC5C,gBAAgB;QAChB,KAAK,EAAE,KAAK;QACZ,OAAO,EAAE,QAAQ;QACjB,SAAS,EAAE,SAAS;KACrB,CAAC,CAAC;IACH,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,MAAM,mCAAmC,GAAG,CAAC,SAAoB,EAAE,EAAE;IACnE,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,sBAAsB,EAAE,GAAG,sCAAsC,CAAC;IAC7F,SAAS,CAAC,IAAI,CACZ,IAAI,EACJ,WAAW,EACX;QACE,SAAS,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,OAAO,CAAC,KAAK,CAAC,CAAC,QAAQ,CAAC,sBAAsB,CAAC,SAAS,CAAC;QACpF,KAAK,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,CAAC;YACpB,kBAAkB;YAClB,cAAc;YACd,YAAY;YACZ,wBAAwB;YACxB,WAAW;YACX,WAAW;YACX,cAAc;YACd,eAAe;YACf,mBAAmB;YACnB,mBAAmB;YACnB,oBAAoB;SACrB,CAAC,CAAC,CAAC,QAAQ,CAAC,sBAAsB,CAAC,KAAK,CAAC;KAC3C,EACD,KAAK,EAAE,MAAW,EAAE,EAAE;QACpB,MAAM,MAAM,GAAG,MAAM,aAAa,CAAC,MAAM,CAAC,CAAA;QAC1C,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,MAAM,CAAC,mCAAmC;iBACjD;aACF;YACD,MAAM,EAAE,MAAM;SACf,CAAA;IACL,CAAC,CAAC,CAAC;AACL,CAAC,CAAC;AACF,OAAO,EAAE,mCAAmC,EAAE,CAAC"}

package/tools/room/get-web-room-integration.js

@@ -0,0 +1,43 @@
+import { z } from 'zod';
+import { GET_WEB_ROOM_UIKIT_INTEGRATION_DEFINITION } from '../definitions/get_web_room_uikit_integration_def.js';
+import { getDocContent } from '../../utils/get-doc-content.js';
+import { reportCLSClient } from '../../utils/report-cls-client.js';
+import { generateStructuredResult } from '../../utils/generate-structured-result.js';
+async function getResultText(params) {
+    const { framework = 'vue' } = params;
+    reportCLSClient({
+        method: 'get_web_room_uikit_integration',
+        framework,
+    });
+    // 获取工作流指令
+    const baseInstructions = getDocContent(['roomkit', framework, 'workflow.md']);
+    // 批量读取目标文档并生成结构化结果
+    const result = await generateStructuredResult({
+        baseInstructions,
+        goals: ['integration'],
+        framework,
+        pathMap: {
+            ['integration']: ['roomkit', framework, 'integration.md'],
+        },
+    });
+    return result;
+}
+const registryGetWebRoomIntegrationTool = (mcpServer) => {
+    const { name, description, parameter_descriptions } = GET_WEB_ROOM_UIKIT_INTEGRATION_DEFINITION;
+    mcpServer.tool(name, description, {
+        framework: z.enum(['vue']).default('vue').describe(parameter_descriptions.framework),
+    }, async (params) => {
+        const result = await getResultText(params);
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: result.llm_code_generation_instructions_md,
+                }
+            ],
+            result: result,
+        };
+    });
+};
+export { registryGetWebRoomIntegrationTool };
+//# sourceMappingURL=get-web-room-integration.js.map

package/tools/room/get-web-room-integration.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get-web-room-integration.js","sourceRoot":"","sources":["../../../src/tools/room/get-web-room-integration.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,yCAAyC,EAAE,MAAM,sDAAsD,CAAC;AACjH,OAAO,EAAE,aAAa,EAAE,MAAM,gCAAgC,CAAC;AAC/D,OAAO,EAAE,eAAe,EAAE,MAAM,kCAAkC,CAAC;AACnE,OAAO,EAAE,wBAAwB,EAAE,MAAM,2CAA2C,CAAC;AAErF,KAAK,UAAU,aAAa,CAAC,MAA2B;IACtD,MAAM,EAAE,SAAS,GAAG,KAAK,EAAE,GAAG,MAAM,CAAC;IACrC,eAAe,CAAC;QACd,MAAM,EAAE,gCAAgC;QACxC,SAAS;KACV,CAAC,CAAC;IACH,UAAU;IACV,MAAM,gBAAgB,GAAG,aAAa,CAAC,CAAC,SAAS,EAAE,SAAS,EAAE,aAAa,CAAC,CAAC,CAAC;IAC9E,mBAAmB;IACnB,MAAM,MAAM,GAAG,MAAM,wBAAwB,CAAC;QAC5C,gBAAgB;QAChB,KAAK,EAAE,CAAC,aAAa,CAAC;QACtB,SAAS;QACT,OAAO,EAAE;YACP,CAAC,aAAa,CAAC,EAAE,CAAC,SAAS,EAAE,SAAS,EAAE,gBAAgB,CAAC;SAC1D;KACF,CAAC,CAAA;IACF,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,MAAM,iCAAiC,GAAG,CAAC,SAAoB,EAAE,EAAE;IACjE,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,sBAAsB,EAAE,GAAG,yCAAyC,CAAC;IAChG,SAAS,CAAC,IAAI,CACZ,IAAI,EACJ,WAAW,EACX;QACE,SAAS,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,OAAO,CAAC,KAAK,CAAC,CAAC,QAAQ,CAAC,sBAAsB,CAAC,SAAS,CAAC;KACrF,EACD,KAAK,EAAE,MAAW,EAAE,EAAE;QACpB,MAAM,MAAM,GAAG,MAAM,aAAa,CAAC,MAAM,CAAC,CAAA;QAC1C,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,MAAM,CAAC,mCAAmC;iBACjD;aACF;YACD,MAAM,EAAE,MAAM;SACf,CAAA;IACL,CAAC,CAAC,CAAC;AACL,CAAC,CAAC;AAEF,OAAO,EAAE,iCAAiC,EAAE,CAAC"}

package/utils/report-cls-client.js

@@ -6,7 +6,7 @@ function reportCLSClient(reportData) {
     const time = Date.now();
     const data = {
         platform: 'mcp',
-        verison: '1.3.1',
+        verison: '1.3.2',
         sdkappid: `${SDKAppID}`,
         method: method,
         userid: userID,

package/utils/report-es-client.js

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

package/resource/doc/chatuikit/flutter/integrate_only_tuichat_Flutter.md

@@ -1,333 +0,0 @@
-Flutter Chat UIKit is designed to provide developers with a comprehensive set of tools to create feature-rich chat applications with ease.
-
-It is built with a modular approach, allowing you to choose the components you need while keeping your application lightweight and efficient.
-
-Among them, the `TencentCloudChatMessage` component offers both private messaging (1V1) and group chat features. It supports a variety of operations on messages, such as sending different types of messages, long-pressing to reply or quote messages, and querying details of read receipts.
-
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027812451/88171fa9126b11efbf645254007bbd8c.png)
-
-
-
-【Mobile】
-
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027812451/2b94a14e128411efa2935254005ac0ca.png)![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027812451/2b895003128411efaa1c525400f65c2a.png)![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027812451/2b9be15d128411ef89cc5254002fd0a8.png)![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027812451/2b85e7f3128411ef83b95254002977b6.png)
-
-【Desktop & Tablet】
-
-**Light**
-
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027812451/49853d30128411efa2935254005ac0ca.png)
-
-
-
-
-**Dark**
-
-![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027812451/49866443128411efbf645254007bbd8c.png)
-
-
-## Features
-1. **Personalized Appearance**: With built-in dark and light modes, the UIKit offers a variety of  theme and appearance customization options to meet your business needs.
-
-2. **Multi-Platform Compatibility**: The adaptable single codebase ensures compatibility across various platforms, including **mobile** devices (iOS/Android), **tablets** (iPad and Android tablets), **web** browsers, and **desktop** environments (Windows/macOS).
-
-3. **Localization Support**: Developed with native English and other language options, including Arabic, Japanese, Korean, Simplified Chinese, and Traditional Chinese. The internationalization features ensure a localized user interface in these languages and support customization and addition of languages, with Arabic featuring support for **RTL** UI.
-
-4. **Enhanced Performance**: The UIKit offers improved performance for message lists, optimized memory usage, and precise message positioning capabilities, catering to scenarios with a large volume of messages and navigation to older messages.
-
-5. **Advanced Features**: The UIKit boasts numerous advanced capabilities, including continuous voice message playback, enhanced multimedia and file message experiences, and intuitive left-right swipe gestures to preview multimedia messages.
-
-6. **Refined User Experience**: Delicate enhancements such as rich animations, haptic feedback, and a polished interface contribute to improved user experiences. New features like grid-style avatars, redesigned forwarding panels, group member selectors, and enhanced long-press message menus further enrich the experiences.
-
-7. **Modular Design**: Components are organized into modular packages, allowing for selective imports and reducing unnecessary bloat. Each package supports built-in navigation transitions, streamlining development and integration by automatically handling transitions, such as those between conversations and messages.
-
-8. **Developer-Friendly Approach**: A more unified and standardized design of component parameters, clearer code naming conventions, and detailed comments, combined with the flexibility to choose between global or instance-level configuration management, make development easier and more efficient.
-
-
-## Compatibility
-
-Our UIKit supports **mobile**, **tablet**, and **desktop** UI designs, and is compatible with Android, iOS, macOS, Windows, and Web (will be supported in future versions).
-
-It comes with built-in support for English, Simplified Chinese, Traditional Chinese, Japanese, Korean, and Arabic (with support for Arabic RTL interface), and both light and dark appearance modes.
-
-## Requirements
-- Flutter version: 3.24 or above
-
-- Dart version: 3.0 or above
-
-
-## Quick Start
-
-### Importing Packages
-
-#### Base Package
-
-To start using our UIKit, first import the base package, tencent_cloud_chat_common.
-``` plaintext
-flutter pub add tencent_cloud_chat
-```
-
-#### Modular Component Packages
-
-Next, import the modular UI component package for message chat, tencent_cloud_chat_message:
-``` plaintext
-flutter pub add tencent_cloud_chat_message
-
-```
-
-> **Platform Integration**
-> 
-
-> Before proceeding to the Basic Usage section, make sure to complete the integration of additional platforms following the steps outlined here, especially if you are targeting these specific platforms for deployment.
-> 
-> - **Web / macOS: **If you plan to deploy your project on ***Web*** or ***macOS*** platforms, see [Expanding to More Platforms](https://www.tencentcloud.com/document/product/1047/45907#more).
-> - **iOS:** Open `ios/Podfile`, and replace the final section with the following content.
-> `post_install do |installer|`
-> `  installer.pods_project.targets.each do |target|`
-> `    flutter_additional_ios_build_settings(target)`
-> `    target.build_configurations.each do |config|        `
-> `          config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'               `
-> `          config.build_settings['ENABLE_BITCODE'] = 'NO'        `
-> `          config.build_settings["ONLY_ACTIVE_ARCH"] = "NO"    `
-> `        end`
-> `    target.build_configurations.each do |config|`
-> `          config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= [`
-> `            '$(inherited)',`
-> `            'PERMISSION_MICROPHONE=1',`
-> `            'PERMISSION_CAMERA=1',`
-> `            'PERMISSION_PHOTOS=1',`
-> `          ]`
-> `        end`
-> `  end`
-> `end`
-> - **Android / Windows: **No additional actions required.
-
-
-### Initializing UIKit
-
-Before you start using each modular package UI component, there are some initial setup steps you need to follow in your project.
-1. Prepare the necessary Chat configuration information, such as sdkappid, test userID, and userSig. For more details, see [Prerequisites](https://www.tencentcloud.com/document/product/1047/45907#.E5.89.8D.E5.BA.8F.E5.B7.A5.E4.BD.9C).
-
-2. **Install Packages:**
-
-
-   In your Flutter project, install the main package and the optional modular packages mentioned in the Quick Start section.
-
-3. **Global Configurations:**
-
-
-   Import `TencentCloudChatMaterialApp`: Replace your project's `MaterialApp` with `TencentCloudChatMaterialApp`. This enables automatic management and configurations of the language, theme *(with material3)*, theme mode, and other settings. It ensures that the UIKit's interface parameters are consistent with your project.
-
-
-   This step will take over the language, theme, and theme mode configurations of your project. If you do not want the automatic management of configurations for your project, you can manually import the features you need into your project according to the **following guide**.
-
-
-   
-
-
-
-
-
-#### Implementing Global Configurations for UIKit Manually
-
-It is recommended to replace your project's `MaterialApp` with `TencentCloudChatMaterialApp`. This enables automatic management of global configurations, including localization, theme, and theme mode.
-
-However, if you want to retain your project's `MaterialApp` due to extensive customization or the use of other packages such as `Get`, you can manually initialize the UIKit. This guide will help you complete the process.
-
-In the global configurations, localization is required, while the theme and theme mode settings are optional. Let us get started.
-
-##### Required Configurations
-- *Localization*
-
-
-First, import the localization tools into your app's entry file.
-``` java
-import 'package:tencent_cloud_chat_intl/localizations/tencent_cloud_chat_localizations.dart';
-```
-
-Next, add the localization configurations to `MaterialApp` or another entry provided by third-party packages like `GetMaterialApp`.
-``` plaintext
-MaterialApp(
-  localizationsDelegates: const [
-    /// Your configurations
-    GlobalMaterialLocalizations.delegate,
-
-    /// Add this line
-    ...TencentCloudChatLocalizations.localizationsDelegates,  /// Add this line
-  ],
-  supportedLocales: [
-    /// Your configurations
-    ...S.delegate.supportedLocales,
-
-    /// Add this line
-    ...TencentCloudChatLocalizations.supportedLocales,
-  ],
-  /// ... Other configurations
-)
-```
-
-Additionally, you can set the language region `locale` according to your business logic, such as recording the user-specified language upon app's launch, instead of following the system settings. This configuration will apply to both your project and the Chat UIKit.
-
-For more information of customizing localization, including adding or removing languages, adding the localization entry, and modifying translation words, see [Internationalization](https://trtc.io/document/52154?platform=flutter&product=chat&menulabel=uikit).
-
-##### Optional Configurations
-- *Theme / Theme Mode*
-
-
-The UIKit's theme data, defined by the `TencentCloudChatTheme` class, is globally maintained and managed through `TencentCloudChat.dataInstance.theme`.
-``` dart
-TencentCloudChatTheme theme = TencentCloudChat.dataInstance.theme;
-```
-
-This theme instance includes a theme model (including the theme data for both light and dark modes) and brightness (the light and dark mode status).
-
-Furthermore, you can specify the `theme` and `darkTheme` from `MaterialApp` using the Material 3 style theme data that we provide for both light and dark modes. You can also set the `themeMode` status based on the brightness status we maintain. This ensures a consistent appearance across your application and our Chat UIKit and enhances the user experiences. (You can customize this theme style as described below.)
-
-To achieve this, we recommend converting your entry widget (which hosts the `MaterialApp`) into a `StatefulWidget`. Add a `TencentCloudChatTheme theme` as part of its state, and listen to `Stream<TencentCloudChatTheme>? themeDataListener` to update its value and build the app based on dynamic, and customizable theme data. Here is the sample code:
-``` dart
-// Theme instance for the Chat UIKit
-TencentCloudChatTheme theme = TencentCloudChat.dataInstance.theme;
-
-// Listener for theme data changes
-Stream<TencentCloudChatTheme>? themeDataListener = TencentCloudChat.eventBusInstance.on<TencentCloudChatTheme>();
-
-// Callback for handling theme data changes
-void _themeDataChangeCallback(TencentCloudChatTheme themeData) {
-  setState(() {
-    theme = themeData;
-  });
-}
-
-// Adds a listener for theme data changes
-void _addThemeDataChangeListener() {
-  themeDataListener?.listen(
-    _themeDataChangeCallback,
-  );
-}
-
-@override
-void initState() {
-  super.initState();
-  _addThemeDataChangeListener();
-}
-
-// .......
-
-return MaterialApp(
-  themeMode: theme.brightness != null ? (theme.brightness == Brightness.light ? ThemeMode.light : ThemeMode.dark) : null,
-  theme: theme.getThemeData(brightness: Brightness.light),
-  darkTheme: theme.getThemeData(brightness: Brightness.dark),
-   /// ... Other configurations
-);
-```
-  - To customize the theme for the Chat UIKit appearance and the global theme (if specified in `MaterialApp` as shown above), use the `TencentCloudChatCoreController.setThemeColors` method to specify the appearance colors for both light and dark modes. For specific usage instructions, see the comments in the code.
-
-  - To switch the theme mode (brightness), use `TencentCloudChatCoreController.setBrightnessMode` or `TencentCloudChatCoreController.toggleBrightnessMode`. For specific usage instructions, see the comments in the code.
-
-
-1. **Initialization and Log-in**:
-
-
-   Call the `TencentCloudChat.controller.initUIKit` method to initialize and log in. The call instructions and reference code are as follows:
-   
-
-   > **Note:**
-   > 
-
-   > We highly recommend configuring the `callbacks` to efficiently handle SDK API errors and specific UIKit events that require user attention through `Dialog` or `Tooltip` in a customizable way.
-   > 
-
-   ``` java
-   await TencentCloudChat.controller.initUIKit(
-     config: TencentCloudChatConfig(), /// [Optional]: The global configurations that affecting the whole chat interface, including user configurations and theme configurations.
-     options: TencentCloudChatInitOptions(
-       sdkAppID: , /// [Required]: The SDKAppID of your Tencent Cloud chat application.
-       userID: , /// [Required]: The userID of the logged-in user.
-       userSig: , /// [Required]: The userSig of the logged-in user.
-     ),
-   
-     components: TencentCloudChatInitComponentsRelated( /// [Required]: Modular UI component settings, effective globally.
-       usedComponentsRegister: [
-         /// [Required]: List of registration functions for the components used in the chat interface.
-         /// Simply use the `register` from TencentCloudChatMessage.
-         TencentCloudChatMessageManager.register,
-       ],
-       componentConfigs: TencentCloudChatComponentConfigs(
-         /// [Optional]: Provide custom configurations for each UI modular component here. These builders will be applied globally.
-       ),
-       componentBuilders: TencentCloudChatComponentBuilders(
-         /// [Optional]: Provide custom UI builders for each UI modular component here. These builders will be applied globally.
-       ),
-       componentEventHandlers: TencentCloudChatComponentEventHandlers(
-         /// [Optional]: Provide custom event handlers for UI component events here. These builders will be applied globally.
-       ),
-     ),
-   
-     /// [Critical]: It is strongly recommended to incorporate the following callback listeners for effectively managing SDK events, SDK API errors and specific UIKit events that require user attention.
-     /// For detailed usage, see the Integrating UIKit Callbacks section at the end of this README document.
-     callbacks: TencentCloudChatCallbacks(
-       onTencentCloudChatSDKEvent: V2TimSDKListener(),  /// [Optional]: Handles SDK events, such as onKickedOffline and onUserSigExpired.
-       onTencentCloudChatSDKFailCallback: (apiName, code, desc) {}, /// [Optional]: Handles SDK API errors.
-       onTencentCloudChatUIKitUserNotificationEvent: (TencentCloudChatComponentsEnum component, TencentCloudChatUserNotificationEvent event) {}, /// [Optional]: Handles specific UIKit events that require user attention on a global scale.across the entire application scope.
-     ),
-   
-     plugins: [],  /// [Optional]: Used plugins, such as tencent_cloud_chat_robot. For specific usage, see the README document of each plugin.
-   );
-   ```
-
-### Initiating a Chat
-
-Chat UIKit offers a comprehensive solution for creating a chat module for users.
-
-By directing to the `TencentCloudChatMessage` with the specified chat user options, you can seamlessly set up a chat module for them. This caters to both one-on-one and group chats.
-
-#### Automatically navigate to the message component.
-
-With the built-in auto-navigation feature, initiating a chat can be easily achieved by calling the `navigateToMessage` method with `TencentCloudChatMessageOptions`, as shown below:
-``` dart
-final messageOptions = TencentCloudChatMessageOptions(
-      // Provide either userID or groupID to indicate the conversation for the chat.
-      userID: "", // For one-on-one chats, provide the other user's userID.
-      groupID: "", // For group chats, provide the groupID.
-    );
-/// Use the messageOptions constructed above.
-navigateToMessage(context: context, options: messageOptions);
-```
-
-By offering either a userID or groupID, the chat conversation can be effortlessly initiated for one-on-one or group chats.
-
-#### Manually Navigating to the Message Component
-
-If you need to manually handle navigation, or wrap the component within your custom pages, then you should instantiate a `TencentCloudChatMessage` component.
-``` dart
-final messageOptions = TencentCloudChatMessageOptions(
-      // Provide either userID or groupID to indicate the conversation for the chat.
-      userID: "", // For one-on-one chats, provide the other user's userID.
-      groupID: "", // For group chats, provide the groupID.
-    );
-    
-final Widget message = TencentCloudChatMessage(
-      options: messageOptions,
-
-      // ... Other parameters, such as builders, can be specified globally or passed in statically here based on your requirements. For detailed usage, see the parameter and method comments.
-    );
-```
-
-You can place this instantiated component in the `build` method of a separate page or use it directly for navigation like using `Navigator.push`.
-
-## Advanced Usage
-
-Once you have implemented the basic usage steps, you will have a chat message module in your project with a default user interface and business logic. However, if these defaults do not fully align with your business requirements, there are several ways to customize the module:
-- Controller: Use the controller to manage the message widgets. This could involve sending additional messages as needed, and scrolling the message list.
-
-- Config: Adjust basic settings using the config.
-
-- Builders: Further customize the UI widgets with the builder. Each builder is equipped with data (essential parameters for building a custom widget), methods (business logic methods), and widgets (the default atomized widgets for each builder).
-
-- EventHandlers: Attach listeners to `eventHandlers` to manage component-specific events. This includes `uiEventHandlers` (such as various events like `onTap`) and `lifeCycleEventHandlers` (such as events triggered after a message has been sent).
-
-
-   These advanced implementation methods are consistent across all Chat UIKit components. For a deeper understanding of these advanced features, you can see [**Advanced Usage**](https://trtc.io/document/58585?platform=flutter&product=chat&menulabel=uikit#93becf46-25ac-456b-bd4c-38db387d8149).
-
-
-   The above steps provide a quick guide to integrating the message chat component individually. If you wish to understand the complete usage of Chat UIKit or have any unresolved issues, see [**UIKit Integration Documentation**](https://trtc.io/document/58585?platform=flutter&product=chat&menulabel=uikit).