Skip to main content

mcix install

Bootstrap a new MCI project with starter configuration.
Creates:
  • mci.json (or mci.yaml) - Main configuration file
  • mci/ directory - Library of toolsets
  • mci/.gitignore - Excludes generated files

mcix list

Display all available tools from your configuration.
Filter types:
  • tags:tag1,tag2 - Include tools with any of these tags
  • only:tool1,tool2 - Include only specific tools
  • except:tool1,tool2 - Exclude specific tools
  • toolsets:ts1,ts2 - Include tools from specific toolsets
  • without-tags:tag1,tag2 - Exclude tools with these tags

mcix validate

Validate your MCI schema for correctness.
Checks for:
  • Schema structure and syntax
  • Required fields
  • Data types
  • Tool definitions
  • Toolset references
  • MCP command availability (warnings)

mcix add

Add toolset references to your schema.
Automatically preserves your file format (JSON stays JSON, YAML stays YAML).

mcix run

Launch an MCP server that dynamically serves your tools.
The server:
  • Loads tools from your MCI schema
  • Converts them to MCP format
  • Listens on STDIO for MCP requests
  • Delegates execution back to MCIClient
Stop the server: Press Ctrl+C

mcix envs

List all environment variables referenced in your MCI configuration.
The envs command scans your entire MCI schema including:
  • Main schema file tools and configuration
  • All referenced toolsets
  • MCP server configurations
Output formats:
  • table (default) - Display variables in a formatted table with locations
  • env - Generate .env.example.mci file with all variables
Example table output:
Example .env file output:
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.