@teambit/cli-mcp-server 0.0.88 → 0.0.90

package/README.docs.mdx

@@ -211,7 +211,7 @@ In default mode, the server exposes a minimal set of essential tools focused on
 
   - `bit_remote_search`: Search for components in remote scopes
   - `bit_workspace_info`: Get comprehensive workspace information including status, components list, apps, templates, and dependency graph
-  - `bit_component_details`: Get detailed information about a specific component including basic info and optionally its public API schema
+  - `bit_component_details`: Get detailed information about multiple components in parallel (up to 5 max) including basic info and optionally their public API schemas
   - `bit_create`: Create a new component (source files and config) using a template with proper argument validation and documentation
   - `bit_query`: Execute read-only Bit commands that safely inspect workspace and component state without making modifications
   - `bit_execute`: Execute any Bit command, including those that modify workspace or repository state (use with caution)
@@ -264,6 +264,44 @@ Search for multiple components in parallel for efficient discovery:
 - Data display: `["table", "pagination", "filter", "sort"]`
 - Button variations: `["button", "btn", "click"]`
 
+### bit_component_details
+
+Get detailed information about multiple components in parallel (limited to 5 components max to prevent context overload):
+
+```json
+{
+  "componentIds": ["acme.design/ui/button", "acme.design/forms/input"],
+  "includeSchema": true,
+  "cwd": "/path/to/workspace"
+}
+```
+
+**Parameters:**
+
+- `componentIds` (required): Array of component IDs to get details for. Limited to 5 components max. Use full component IDs (e.g., `acme.design/ui/button`)
+- `cwd` (required): Path to workspace directory
+- `includeSchema` (optional): Include component public API schema (default: false)
+
+**Examples:**
+
+- Multiple UI components: `{"componentIds": ["acme.design/ui/button", "acme.design/ui/input", "acme.design/ui/dropdown"], "cwd": "/path/to/workspace"}`
+- With schema information: `{"componentIds": ["teambit.base-ui/navigation/link"], "includeSchema": true, "cwd": "/path/to/workspace"}`
+- Form components batch: `{"componentIds": ["acme.forms/input", "acme.forms/validation", "acme.forms/submit-button"], "cwd": "/path/to/workspace"}`
+
+**Response Format:**
+
+The tool returns a structured response with:
+
+- `summary`: Statistics about the request (requested, successful, failed counts)
+- `components`: Object containing successful component details keyed by component ID
+- `failures`: Object containing error messages for failed components (if any)
+
+**Error Handling:**
+
+- Returns error if more than 5 components are requested
+- Individual component failures don't block the entire request
+- Clear error messages indicate which specific components failed and why
+
 ### bit_create
 
 Create a new component with template-based generation:

package/dist/README.docs.mdx

@@ -211,7 +211,7 @@ In default mode, the server exposes a minimal set of essential tools focused on
 
   - `bit_remote_search`: Search for components in remote scopes
   - `bit_workspace_info`: Get comprehensive workspace information including status, components list, apps, templates, and dependency graph
-  - `bit_component_details`: Get detailed information about a specific component including basic info and optionally its public API schema
+  - `bit_component_details`: Get detailed information about multiple components in parallel (up to 5 max) including basic info and optionally their public API schemas
   - `bit_create`: Create a new component (source files and config) using a template with proper argument validation and documentation
   - `bit_query`: Execute read-only Bit commands that safely inspect workspace and component state without making modifications
   - `bit_execute`: Execute any Bit command, including those that modify workspace or repository state (use with caution)
@@ -264,6 +264,44 @@ Search for multiple components in parallel for efficient discovery:
 - Data display: `["table", "pagination", "filter", "sort"]`
 - Button variations: `["button", "btn", "click"]`
 
+### bit_component_details
+
+Get detailed information about multiple components in parallel (limited to 5 components max to prevent context overload):
+
+```json
+{
+  "componentIds": ["acme.design/ui/button", "acme.design/forms/input"],
+  "includeSchema": true,
+  "cwd": "/path/to/workspace"
+}
+```
+
+**Parameters:**
+
+- `componentIds` (required): Array of component IDs to get details for. Limited to 5 components max. Use full component IDs (e.g., `acme.design/ui/button`)
+- `cwd` (required): Path to workspace directory
+- `includeSchema` (optional): Include component public API schema (default: false)
+
+**Examples:**
+
+- Multiple UI components: `{"componentIds": ["acme.design/ui/button", "acme.design/ui/input", "acme.design/ui/dropdown"], "cwd": "/path/to/workspace"}`
+- With schema information: `{"componentIds": ["teambit.base-ui/navigation/link"], "includeSchema": true, "cwd": "/path/to/workspace"}`
+- Form components batch: `{"componentIds": ["acme.forms/input", "acme.forms/validation", "acme.forms/submit-button"], "cwd": "/path/to/workspace"}`
+
+**Response Format:**
+
+The tool returns a structured response with:
+
+- `summary`: Statistics about the request (requested, successful, failed counts)
+- `components`: Object containing successful component details keyed by component ID
+- `failures`: Object containing error messages for failed components (if any)
+
+**Error Handling:**
+
+- Returns error if more than 5 components are requested
+- Individual component failures don't block the entire request
+- Clear error messages indicate which specific components failed and why
+
 ### bit_create
 
 Create a new component with template-based generation:

package/dist/cli-mcp-server.main.runtime.d.ts

@@ -85,7 +85,7 @@ export declare class CliMcpServerMain {
     getEditorConfigPath(editor: string, isGlobal: boolean, workspaceDir?: string): string;
     setupEditor(editor: string, options: SetupOptions, workspaceDir?: string): Promise<void>;
     writeRulesFile(editor: string, options: RulesOptions, workspaceDir?: string): Promise<void>;
-    getRulesContent(consumerProject?: boolean): Promise<string>;
+    getRulesContent(consumerProject?: boolean, forceStandard?: boolean): Promise<string>;
     static slots: never[];
     static dependencies: import("@teambit/harmony").Aspect[];
     static runtime: import("@teambit/harmony").RuntimeDefinition;

package/dist/cli-mcp-server.main.runtime.js

@@ -858,20 +858,102 @@ class CliMcpServerMain {
   }
   registerComponentDetailsTool(server) {
     const toolName = 'bit_component_details';
-    const description = 'Get detailed information about a specific component including basic info and optionally its public API schema';
+    const description = 'Get detailed information about multiple components in parallel. Supports batch requests for efficient component discovery. Limited to 5 components max to prevent context overload.';
     const schema = {
       cwd: _zod().z.string().describe('Path to workspace directory'),
-      componentName: _zod().z.string().describe('Component name or component ID to get details for'),
+      componentIds: _zod().z.array(_zod().z.string()).describe('Array of component IDs to get details for. Limited to 5 components max. Examples: ["acme.design/ui/button", "acme.design/forms/input", "teambit.base-ui/navigation/link"]'),
       includeSchema: _zod().z.boolean().optional().describe('Include component public API schema (default: false)')
     };
     server.tool(toolName, description, schema, async params => {
       try {
+        // Validate that componentIds parameter is provided and valid
+        if (!params.componentIds || !Array.isArray(params.componentIds) || params.componentIds.length === 0) {
+          return {
+            content: [{
+              type: 'text',
+              text: 'Error: componentIds parameter must be provided as a non-empty array of component IDs. Example: ["acme.design/ui/button", "acme.design/forms/input"]'
+            }]
+          };
+        }
         const includeSchema = params.includeSchema === true;
-        const componentName = params.componentName;
+        const componentIds = params.componentIds;
+
+        // Check limit of 5 components to prevent context overload
+        const maxComponents = 5;
+        if (componentIds.length > maxComponents) {
+          return {
+            content: [{
+              type: 'text',
+              text: `Error: Too many components requested. Maximum allowed is ${maxComponents} components, but ${componentIds.length} were requested. Please reduce the number of components in your request.`
+            }]
+          };
+        }
 
-        // Get component details using IDE API with includeSchema parameter
-        const ideApiResult = await this.callBitServerIDEAPI('getCompDetails', [componentName, includeSchema], params.cwd);
-        return this.formatAsCallToolResult(ideApiResult);
+        // Execute component detail requests in parallel
+        this.logger.debug(`[MCP-DEBUG] Fetching details for ${componentIds.length} component(s) in parallel: ${componentIds.join(', ')}`);
+        const detailPromises = componentIds.map(async componentId => {
+          try {
+            const result = await this.callBitServerIDEAPI('getCompDetails', [componentId, includeSchema], params.cwd);
+            return {
+              componentId,
+              success: true,
+              details: result
+            };
+          } catch (error) {
+            this.logger.warn(`[MCP-DEBUG] Failed to get details for component "${componentId}": ${error.message}`);
+            return {
+              componentId,
+              success: false,
+              error: error.message
+            };
+          }
+        });
+        const detailResults = await Promise.all(detailPromises);
+
+        // Process and consolidate results
+        const successfulResults = detailResults.filter(r => r.success);
+        const failedResults = detailResults.filter(r => !r.success);
+        if (successfulResults.length === 0) {
+          let message = 'Failed to get details for any components';
+          if (failedResults.length > 0) {
+            message += '\n\nErrors:';
+            failedResults.forEach(r => {
+              message += `\n- "${r.componentId}": ${r.error}`;
+            });
+          }
+          return {
+            content: [{
+              type: 'text',
+              text: message
+            }]
+          };
+        }
+
+        // Build the response
+        const response = {
+          summary: {
+            requested: componentIds.length,
+            successful: successfulResults.length,
+            failed: failedResults.length,
+            includeSchema
+          },
+          components: {}
+        };
+
+        // Add successful component details
+        successfulResults.forEach(result => {
+          response.components[result.componentId] = result.details;
+        });
+
+        // Add failed components info if any
+        if (failedResults.length > 0) {
+          response.failures = {};
+          failedResults.forEach(result => {
+            response.failures[result.componentId] = result.error;
+          });
+        }
+        this.logger.debug(`[MCP-DEBUG] Component details fetched: ${successfulResults.length} successful, ${failedResults.length} failed`);
+        return this.formatAsCallToolResult(response);
       } catch (error) {
         this.logger.error(`[MCP-DEBUG] Error in bit_component_details tool: ${error.message}`);
         return this.formatErrorAsCallToolResult(error, 'getting component details');
@@ -1305,8 +1387,8 @@ class CliMcpServerMain {
     }
     await _mcp2().McpConfigWriter.writeRulesFile(editor, rulesOptions);
   }
-  async getRulesContent(consumerProject = false) {
-    return _mcp2().McpConfigWriter.getDefaultRulesContent(consumerProject);
+  async getRulesContent(consumerProject = false, forceStandard = false) {
+    return _mcp2().McpConfigWriter.getDefaultRulesContent(consumerProject, process.cwd(), forceStandard);
   }
   static async provider([cli, loggerMain]) {
     const logger = loggerMain.createLogger(_cliMcpServer().CliMcpServerAspect.id);