Skip to main content

​
CLI Usage & Command Reference

The Sigyl CLI (sigyl) provides tools for integrating, generating, running, and managing Model Context Protocol (MCP) servers and endpoints for Express/Node.js applications. Below is a comprehensive reference of all available commands, their descriptions, and example usages.

​
Table of Contents

​
init

Description: Create a template MCP server with sample tools. Options:
  • -o, --out <directory>: Output directory (default: .mcp-generated)
  • -l, --language <language>: Server language (typescript|javascript, default: typescript)
  • -n, --name <name>: Server name (default: my-mcp-server)
Example: 
sigyl init --out my-mcp-server --language typescript --name demo-server

​
integrate

Description: Integrate MCP endpoints into your existing Express app (recommended developer flow). Options:
  • --out <directory>: Output directory for integration code (default: .sigyl-mcp)
  • --endpoint <path>: MCP endpoint path (default: /mcp)
  • --auto-add: (Coming soon) Automatically add integration to your app
  • -l, --language <language>: Server language (typescript|javascript, default: typescript)
  • [directory]: Directory containing Express app (default: .)
Example: 
sigyl integrate --out .sigyl-mcp --endpoint /mcp ./my-express-app

​
inspect

Description: Launch MCP Inspector to test your server or endpoint. Arguments:
  • [server-path]: Path or URL to MCP server (default: .sigyl-mcp/integration or .mcp-generated/server.js)
Example: 
sigyl inspect .sigyl-mcp/integration

​
install

Description: Install a remote MCP server in a desktop client (claude, cursor, vscode). Accepts a package name or identifier. Arguments:
  • <package>: MCP server package name or identifier (e.g. kazumah1/mcp-test)
Options:
  • -n, --name <name>: Custom name for the server in the client
  • -l, --list: List currently installed MCP servers
  • -r, --remove <name>: Remove an MCP server from the client
  • --client <client>: Target client: claude, cursor, vscode (default: claude)
  • --env <key=value>: Environment variables (can be used multiple times)
  • --cwd <path>: Working directory for the server
  • --key <key>: API key for the MCP server
Examples: 
sigyl install kazumah1/mcp-test --client claude --key <API_KEY>
sigyl install --list
sigyl install --remove my-mcp-server

​
run

Description: Run a remote MCP server as a local proxy for Claude Desktop. Arguments:
  • <package>: MCP package slug (@github-username/repo-name)
Options:
  • --key <key>: API key for authentication
  • --endpoint <endpoint>: Custom endpoint URL (optional)
Example: 
sigyl run kazumah1/mcp-test --key <API_KEY>

​
wizard

Description: Launch interactive setup wizard for common tasks (init, integrate, inspect). Example: 
sigyl wizard

​
config

Description: Configure CLI settings and show current configuration. Subcommands:
  • show: Show current configuration
Example: 
sigyl config show

​
Legacy Commands

​
scan

Description: Scan Express application and generate standalone MCP server (legacy/advanced).Options:
  • [directory]: Directory to scan (default: current directory)
  • -o, --out <directory>: Output directory for generated server (default: .mcp-generated)
  • -p, --port <port>: Port where your Express app runs (default: 3000)
  • -l, --language <language>: Server language (typescript|javascript, default: typescript)
  • --framework <framework>: Web framework (default: express)
Example:
sigyl scan ./my-express-app --out .mcp-generated --port 4000 --language javascript

​
dev

Description: Start development mode with hot reload (legacy).Options:
  • [directory]: Directory containing Express app (default: .)
  • -p, --port <port>: MCP server port (default: 8181)
  • --app-port <port>: Express app port (default: 3000)
  • -l, --language <language>: Server language (typescript|javascript, default: typescript)
  • --no-open: Don’t open MCP Inspector automatically
Example:
sigyl dev ./my-express-app --port 9000 --app-port 4000 --language javascript --no-open

​
clean

Description: Clean generated MCP server files (legacy).Options:
  • -o, --out <directory>: Output directory to clean (default: .mcp-generated)
Example:
sigyl clean --out .mcp-generated

​
build

Description: Build MCP server from TypeScript to JavaScript (legacy).Arguments:
  • [directory]: Directory containing MCP server (default: .mcp-generated)
Example:
sigyl build .mcp-generated

​
Notes

  • For more details on each command, run sigyl <command> --help.
  • Some commands are marked as legacy and may be replaced by improved flows in the future.