@teambit/cli-mcp-server 0.0.11 → 0.0.13

package/README.docs.mdx

@@ -37,42 +37,61 @@ Options:
 - `--include-additional <commands>`: Add specific commands to the default set (comma-separated list)
 - `--exclude <commands>`: Prevent specific commands from being exposed (comma-separated list)
 
-### Integrating with VS Code
+### Integrating with IDEs
 
-To use this MCP server in VS Code:
+The easiest way to integrate the MCP server with your IDE is to use the `setup` command:
 
-1. Open VS Code settings (JSON) by pressing `Ctrl + Shift + P` and typing `Preferences: Open Settings (JSON)`
-2. Add the following JSON block:
+```bash
+# Basic setup for VS Code (default)
+bit mcp-server setup
+```
 
-```json
-{
-  "mcp": {
-    "servers": {
-      "bit-cli": {
-        "command": "bit",
-        "args": ["mcp-server"]
-      }
-    }
-  }
-}
+This will automatically configure your VS Code settings to use the Bit MCP server. See the [Automatic Setup](#automatic-integration-setup) section below for more options.
+
+### Automatic Integration Setup
+
+The **recommended way** to integrate the MCP server with your IDE is using the `setup` command:
+
+```bash
+bit mcp-server setup [vscode|cursor|windsurf] [options]
 ```
 
-For extended mode with all commands available:
+This command automatically configures the MCP server settings in your chosen editor. If no editor is specified, it defaults to VS Code.
 
-```json
-{
-  "mcp": {
-    "servers": {
-      "bit-cli": {
-        "command": "bit",
-        "args": ["mcp-server", "--extended"]
-      }
-    }
-  }
-}
+#### Supported Editors
+
+- **VS Code**: `bit mcp-server setup vscode` (or just `bit mcp-server setup`)
+- **Cursor**: `bit mcp-server setup cursor`
+- **Windsurf**: `bit mcp-server setup windsurf`
+
+#### Configuration Options
+
+- `--global`: Apply configuration globally (user settings) instead of workspace settings
+- `--extended`: Configure with extended mode enabled
+- `--consumer-project`: Configure for consumer projects
+- `--include-only <commands>`: Specify subset of commands to expose
+- `--include-additional <commands>`: Add specific commands to the default set
+- `--exclude <commands>`: Prevent specific commands from being exposed
+
+#### Examples
+
+```bash
+# Basic VS Code setup (workspace level)
+bit mcp-server setup
+
+# Global setup for Cursor with extended mode
+bit mcp-server setup cursor --global --extended
+
+# Setup for Windsurf with consumer project mode
+bit mcp-server setup windsurf --consumer-project
 ```
 
-For consumer projects that only use Bit component packages:
+#### Manual Configuration
+
+If you need to manually configure the settings, here's a basic example for VS Code:
+
+1. Open VS Code settings (JSON) by pressing `Ctrl + Shift + P` (or `Cmd + Shift + P` on macOS) and typing `Preferences: Open Settings (JSON)`
+2. Add the following configuration:
 
 ```json
 {
@@ -80,7 +99,7 @@ For consumer projects that only use Bit component packages:
     "servers": {
       "bit-cli": {
         "command": "bit",
-        "args": ["mcp-server", "--consumer-project"]
+        "args": ["mcp-server"]
       }
     }
   }
@@ -122,7 +141,10 @@ In default mode, the server exposes a minimal set of essential tools focused on
 
   - `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_commands_info`: Get information about available Bit commands and their groups
+  - `bit_commands_list`: Get all available Bit commands with descriptions and groups (for command discovery)
+  - `bit_command_help`: Get detailed help for a specific Bit command including syntax, arguments, flags, and usage examples
+
+> **Command Discovery vs. Command Help**: Use `bit_commands_list` to discover what commands are available in Bit, then use `bit_command_help` with a specific command name to get detailed usage information including arguments, flags, and examples.
 
 - **Generic Execution Tools:**
   - `bit_query`: Execute read-only Bit commands that safely inspect workspace and component state without making modifications

package/dist/README.docs.mdx

@@ -37,42 +37,61 @@ Options:
 - `--include-additional <commands>`: Add specific commands to the default set (comma-separated list)
 - `--exclude <commands>`: Prevent specific commands from being exposed (comma-separated list)
 
-### Integrating with VS Code
+### Integrating with IDEs
 
-To use this MCP server in VS Code:
+The easiest way to integrate the MCP server with your IDE is to use the `setup` command:
 
-1. Open VS Code settings (JSON) by pressing `Ctrl + Shift + P` and typing `Preferences: Open Settings (JSON)`
-2. Add the following JSON block:
+```bash
+# Basic setup for VS Code (default)
+bit mcp-server setup
+```
 
-```json
-{
-  "mcp": {
-    "servers": {
-      "bit-cli": {
-        "command": "bit",
-        "args": ["mcp-server"]
-      }
-    }
-  }
-}
+This will automatically configure your VS Code settings to use the Bit MCP server. See the [Automatic Setup](#automatic-integration-setup) section below for more options.
+
+### Automatic Integration Setup
+
+The **recommended way** to integrate the MCP server with your IDE is using the `setup` command:
+
+```bash
+bit mcp-server setup [vscode|cursor|windsurf] [options]
 ```
 
-For extended mode with all commands available:
+This command automatically configures the MCP server settings in your chosen editor. If no editor is specified, it defaults to VS Code.
 
-```json
-{
-  "mcp": {
-    "servers": {
-      "bit-cli": {
-        "command": "bit",
-        "args": ["mcp-server", "--extended"]
-      }
-    }
-  }
-}
+#### Supported Editors
+
+- **VS Code**: `bit mcp-server setup vscode` (or just `bit mcp-server setup`)
+- **Cursor**: `bit mcp-server setup cursor`
+- **Windsurf**: `bit mcp-server setup windsurf`
+
+#### Configuration Options
+
+- `--global`: Apply configuration globally (user settings) instead of workspace settings
+- `--extended`: Configure with extended mode enabled
+- `--consumer-project`: Configure for consumer projects
+- `--include-only <commands>`: Specify subset of commands to expose
+- `--include-additional <commands>`: Add specific commands to the default set
+- `--exclude <commands>`: Prevent specific commands from being exposed
+
+#### Examples
+
+```bash
+# Basic VS Code setup (workspace level)
+bit mcp-server setup
+
+# Global setup for Cursor with extended mode
+bit mcp-server setup cursor --global --extended
+
+# Setup for Windsurf with consumer project mode
+bit mcp-server setup windsurf --consumer-project
 ```
 
-For consumer projects that only use Bit component packages:
+#### Manual Configuration
+
+If you need to manually configure the settings, here's a basic example for VS Code:
+
+1. Open VS Code settings (JSON) by pressing `Ctrl + Shift + P` (or `Cmd + Shift + P` on macOS) and typing `Preferences: Open Settings (JSON)`
+2. Add the following configuration:
 
 ```json
 {
@@ -80,7 +99,7 @@ For consumer projects that only use Bit component packages:
     "servers": {
       "bit-cli": {
         "command": "bit",
-        "args": ["mcp-server", "--consumer-project"]
+        "args": ["mcp-server"]
       }
     }
   }
@@ -122,7 +141,10 @@ In default mode, the server exposes a minimal set of essential tools focused on
 
   - `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_commands_info`: Get information about available Bit commands and their groups
+  - `bit_commands_list`: Get all available Bit commands with descriptions and groups (for command discovery)
+  - `bit_command_help`: Get detailed help for a specific Bit command including syntax, arguments, flags, and usage examples
+
+> **Command Discovery vs. Command Help**: Use `bit_commands_list` to discover what commands are available in Bit, then use `bit_command_help` with a specific command name to get detailed usage information including arguments, flags, and examples.
 
 - **Generic Execution Tools:**
   - `bit_query`: Execute read-only Bit commands that safely inspect workspace and component state without making modifications

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

@@ -1,6 +1,7 @@
 import { CLIMain } from '@teambit/cli';
 import { Logger, LoggerMain } from '@teambit/logger';
 import { Http } from '@teambit/scope.network';
+import { SetupOptions } from './setup-utils';
 export declare class CliMcpServerMain {
     private cli;
     private logger;
@@ -22,6 +23,14 @@ export declare class CliMcpServerMain {
      * Call bit-server API endpoint using cli-raw route
      */
     private callBitServerAPI;
+    /**
+     * Call bit-server API endpoint using IDE route
+     */
+    private callBitServerIDEAPI;
+    /**
+     * Generic method to call bit-server API with different routes
+     */
+    private callBitServerAPIWithRoute;
     runMcpServer(options: {
         extended?: boolean;
         includeOnly?: string;
@@ -39,7 +48,8 @@ export declare class CliMcpServerMain {
     private registerRemoteSearchTool;
     private registerWorkspaceInfoTool;
     private registerComponentDetailsTool;
-    private registerCommandsInfoTool;
+    private registerCommandsListTool;
+    private registerCommandHelpTool;
     private registerQueryTool;
     private registerExecuteTool;
     private processSubCommands;
@@ -60,6 +70,8 @@ export declare class CliMcpServerMain {
      * Helper method to safely execute a bit command with error handling
      */
     private safeBitCommandExecution;
+    getEditorDisplayName(editor: string): string;
+    setupEditor(editor: string, options: SetupOptions, workspaceDir?: string): Promise<void>;
     static slots: never[];
     static dependencies: import("@teambit/harmony").Aspect[];
     static runtime: import("@teambit/harmony").RuntimeDefinition;