command names

Author: MaestroError

PLAN.md

@@ -135,7 +135,7 @@ None for this stage.
 
 ---
 
-## Stage 3: CLI Command: `mci install`
+## Stage 3: CLI Command: `mcix install`
 
 ### Goal
 Implement the `install` command to initialize MCI project structure.
@@ -158,7 +158,7 @@ src/mci/cli/
 - **src/mci/mci.py** - Register install command
 
 ### Classes/Functions
-- `install_command(yaml: bool = False)` - Click command for `mci install`
+- `install_command(yaml: bool = False)` - Click command for `mcix install`
 - `create_mci_file(format: str) -> None` - Create main MCI file
 - `create_mci_directory() -> None` - Create ./mci directory structure
 - `create_example_toolset() -> None` - Create example.mci.json
@@ -301,7 +301,7 @@ src/mci/core/
 
 ---
 
-## Stage 5: CLI Command: `mci list`
+## Stage 5: CLI Command: `mcix list`
 
 ### Goal
 Implement the `list` command to display available tools.
@@ -382,7 +382,7 @@ src/mci/cli/
 
 ---
 
-## Stage 6: CLI Command: `mci validate`
+## Stage 6: CLI Command: `mcix validate`
 
 ### Goal
 Implement the `validate` command to check MCI schema correctness using mci-py's built-in validation.
@@ -409,7 +409,7 @@ src/mci/core/
 - **src/mci/mci.py** - Register validate command
 
 ### Classes/Functions
-- `validate_command(file: str)` - Click command for `mci validate`
+- `validate_command(file: str)` - Click command for `mcix validate`
 - `MCIValidator` class with methods:
   - `validate_schema(file_path: str) -> ValidationResult` - Validate using MCIClient
   - `check_toolset_files() -> list[ValidationWarning]` - Check toolset file existence
@@ -449,7 +449,7 @@ src/mci/core/
 
 ---
 
-## Stage 7: CLI Command: `mci add`
+## Stage 7: CLI Command: `mcix add`
 
 ### Goal
 Implement the `add` command to add toolset references to MCI files.
@@ -573,7 +573,7 @@ src/mci/core/
 
 ---
 
-## Stage 9: CLI Command: `mci run` (STDIO Only)
+## Stage 9: CLI Command: `mcix run` (STDIO Only)
 
 ### Goal
 Implement the `run` command to launch MCP servers via STDIO that serve MCI tools.
@@ -605,7 +605,7 @@ src/mci/core/
 - **src/mci/mci.py** - Register run command
 
 ### Classes/Functions
-- `run_command(file: str, filter: str)` - Click command for `mci run`
+- `run_command(file: str, filter: str)` - Click command for `mcix run`
 - `DynamicMCPServer` class with async methods:
   - `async create_from_mci_schema(schema_path: str, filter_spec: str = None) -> Server`
     - Load tools using MCIClient from Stage 4
@@ -819,7 +819,7 @@ Stage 2 (Config Loading)
 
 These features are documented in PRD.md but not included in the initial 10 stages:
 
-1. **Stage 11** (Future): `mci run --port` for HTTP-based MCP servers
+1. **Stage 11** (Future): `mcix run --port` for HTTP-based MCP servers
 2. **Stage 12** (Future): `mci test` command to simulate tool execution
 3. **Stage 13** (Future): Plugin system for custom commands
 4. **Stage 14** (Future): Interactive mode with prompts

README.md

@@ -119,7 +119,7 @@ Toolsets are collections of related tools stored in the `mci/` directory. They c
 
 ### MCP Server Integration
 
-The `mci run` command creates an MCP server that:
+The `mcix run` command creates an MCP server that:
 
 - Dynamically loads tools from your MCI schema
 - Serves them via the Model Context Protocol
@@ -128,7 +128,7 @@ The `mci run` command creates an MCP server that:
 
 ## Available Commands
 
-### `mci install`
+### `mcix install`
 
 Bootstrap a new MCI project with starter configuration.
 
@@ -145,7 +145,7 @@ Creates:
 - `mci/` directory - Library of toolsets
 - `mci/.gitignore` - Excludes generated files
 
-### `mci list`
+### `mcix list`
 
 Display all available tools from your configuration.
 
@@ -227,7 +227,7 @@ GITHUB_TOKEN=
 
 > **Tip**: Run `uvx mcix envs --format=env` to generate a template `.env.example.mci` file, then copy it to `.env.mci` and fill in your values. Commit `.env.example.mci` to your repository so team members know what environment variables are needed.
 
-### `mci validate`
+### `mcix validate`
 
 Validate your MCI schema for correctness.
 
@@ -247,7 +247,7 @@ Checks for:
 - Toolset references
 - MCP command availability (warnings)
 
-### `mci add`
+### `mcix add`
 
 Add toolset references to your schema.
 
@@ -267,7 +267,7 @@ uvx mcix add weather-tools --path=custom.mci.json
 
 Automatically preserves your file format (JSON stays JSON, YAML stays YAML).
 
-### `mci run`
+### `mcix run`
 
 Launch an MCP server that dynamically serves your tools.
 
@@ -837,7 +837,7 @@ uvx mcix run
 
 ## Integration with MCP Clients
 
-The `mci run` command creates an MCP-compliant server that can be used with:
+The `mcix run` command creates an MCP-compliant server that can be used with:
 
 - **Claude Desktop**: Configure as an MCP server in settings
 - **MCP CLI tools**: Connect via STDIO transport

development.md

@@ -43,11 +43,11 @@ src/mci/
 ├── mci.py               # Main CLI entry point with Click group
 ├── cli/                 # CLI command modules
 │   ├── __init__.py
-│   ├── install.py       # mci install command
-│   ├── list.py          # mci list command
-│   ├── validate.py      # mci validate command
-│   ├── add.py           # mci add command
-│   ├── run.py           # mci run command
+│   ├── install.py       # mcix install command
+│   ├── list.py          # mcix list command
+│   ├── validate.py      # mcix validate command
+│   ├── add.py           # mcix add command
+│   ├── run.py           # mcix run command
 │   └── formatters/      # Output formatters (JSON, YAML, table)
 ├── core/                # Core business logic
 │   ├── __init__.py

docs/architecture.md

@@ -259,7 +259,7 @@ Return filtered tools
 ### MCP Server Creation Flow
 
 ```
-User runs `mci run`
+User runs `mcix run`
     ↓
 Load MCI schema via MCIConfig
     ↓

mci-docs/python/concepts/mcp_servers.mdx

@@ -554,7 +554,7 @@ Only load tools you actually need:
 }
 ```
 
-> Note: MCIClient object supports env_vars as well as when registering with `uvx mci run` in any MCP client (For example, cursor or vscode) you can pass env variables, which will be resolved in whole "mci.json" file, as well as in "mcp_servers" part
+> Note: MCIClient object supports env_vars as well as when registering with `uvx mcix run` in any MCP client (For example, cursor or vscode) you can pass env variables, which will be resolved in whole "mci.json" file, as well as in "mcp_servers" part
 
 ### 4. Add to .gitignore
 

src/mci/cli/add.py

@@ -1,7 +1,7 @@
 """
 add.py - CLI command to add toolset references to MCI schemas
 
-This module provides the `mci add` command which adds toolset references
+This module provides the `mcix add` command which adds toolset references
 to MCI schema files with optional filtering, while preserving the original
 file format (JSON or YAML).
 """
@@ -43,19 +43,19 @@ def add(toolset_name: str, filter: str | None, path: str | None) -> None:
 
         \b
         # Add a toolset without filter
-        mci add weather-tools
+        mcix add weather-tools
 
         \b
         # Add a toolset with "only" filter
-        mci add analytics --filter=only:Tool1,Tool2
+        mcix add analytics --filter=only:Tool1,Tool2
 
         \b
         # Add a toolset with "tags" filter
-        mci add api-tools --filter=tags:api,database
+        mcix add api-tools --filter=tags:api,database
 
         \b
         # Add to a custom file
-        mci add weather-tools --path=custom.mci.json
+        mcix add weather-tools --path=custom.mci.json
     """
     console = Console()
 
@@ -65,7 +65,7 @@ def add(toolset_name: str, filter: str | None, path: str | None) -> None:
         schema_file = file_finder.find_mci_file()
         if schema_file is None:
             console.print("[red]❌ No MCI schema file found in current directory[/red]\n")
-            console.print("[yellow]💡 Run 'mci install' to create a default mci.json file[/yellow]")
+            console.print("[yellow]💡 Run 'mcix install' to create a default mci.json file[/yellow]")
             sys.exit(1)
     else:
         schema_file = path

src/mci/cli/envs.py

@@ -193,7 +193,7 @@ def envs_command(file: str | None, format: str):
             if file is None:
                 console.print(
                     "[red]✗[/red] No MCI schema file found. "
-                    "Run 'mci install' to create one or specify --file.",
+                    "Run 'mcix install' to create one or specify --file.",
                     style="red",
                 )
                 raise click.Abort()

src/mci/cli/install.py

@@ -143,5 +143,5 @@ def install(yaml: bool):
     click.echo()
     click.echo("Next steps:")
     click.echo("  1. Review the generated configuration files")
-    click.echo("  2. Run 'mci list' to see available tools")
-    click.echo("  3. Run 'mci validate' to check your configuration")
+    click.echo("  2. Run 'mcix list' to see available tools")
+    click.echo("  3. Run 'mcix validate' to check your configuration")

src/mci/cli/list.py

@@ -57,22 +57,22 @@ def list_command(file: str | None, filter: str | None, format: str, verbose: boo
     Examples:
 
         # List all tools in table format
-        mci list
+        mcix list
 
         # List tools from specific file
-        mci list --file=./custom.mci.json
+        mcix list --file=./custom.mci.json
 
         # List tools with filter
-        mci list --filter=tags:api,database
+        mcix list --filter=tags:api,database
 
         # List tools with verbose output
-        mci list --verbose
+        mcix list --verbose
 
         # Export tools to JSON file
-        mci list --format=json
+        mcix list --format=json
 
         # Export tools to YAML file with verbose info
-        mci list --format=yaml --verbose
+        mcix list --format=yaml --verbose
     """
     console = Console()
 
@@ -84,7 +84,7 @@ def list_command(file: str | None, filter: str | None, format: str, verbose: boo
             if file is None:
                 console.print(
                     "[red]✗[/red] No MCI schema file found. "
-                    "Run 'mci install' to create one or specify --file.",
+                    "Run 'mcix install' to create one or specify --file.",
                     style="red",
                 )
                 raise click.Abort()

src/mci/cli/run.py

@@ -1,7 +1,7 @@
 """
 run.py - Run command for starting MCP servers from MCI schemas
 
-This module implements the `mci run` command, which launches an MCP server
+This module implements the `mcix run` command, which launches an MCP server
 over STDIO that dynamically serves tools from an MCI schema file. The server
 loads tools using MCIClient, converts them to MCP format, and delegates
 execution back to MCIClient.
@@ -51,22 +51,22 @@ def run(file: str | None, filter: str | None):
     Examples:
 
         # Run server with default mci.json or mci.yaml
-        mci run
+        mcix run
 
         # Run server with specific file
-        mci run --file=./custom.mci.json
+        mcix run --file=./custom.mci.json
 
         # Run server with filtered tools
-        mci run --filter=tags:api,database
+        mcix run --filter=tags:api,database
 
         # Run server with only specific tools
-        mci run --filter=only:tool1,tool2
+        mcix run --filter=only:tool1,tool2
 
         # Run server excluding specific tools
-        mci run --filter=except:tool3,tool4
+        mcix run --filter=except:tool3,tool4
 
         # Run server with tools from specific toolsets
-        mci run --filter=toolsets:weather,database
+        mcix run --filter=toolsets:weather,database
     """
     console = Console()
 
@@ -78,7 +78,7 @@ def run(file: str | None, filter: str | None):
             if file is None:
                 console.print(
                     "[red]✗[/red] No MCI schema file found. "
-                    "Run 'mci install' to create one or specify --file.",
+                    "Run 'mcix install' to create one or specify --file.",
                     style="red",
                 )
                 raise click.Abort()