Igris CLI
The Igris CLI is your terminal interface for MCP governance. It scans configs for security issues, sets up the Igris proxy with one command, monitors sessions, and manages policies — all from the terminal.Installation
Commands
igris (Interactive Menu)
Run igris with no subcommand to open the interactive menu:
- Setup proxy for MCP servers — discover, scan, and proxy your MCP configs
- Scan configs for security issues — run the scanner across all configs
- View sessions & status — see active sessions and recent events
- Manage policies — view governance policies
login / logout / whoami
Authenticate with your Igris API key:
~/.igris/credentials.json.
init
Interactive proxy setup wizard. Discovers MCP configs, scans them, registers servers, and rewrites configs to route through the Igris proxy.
- Checks authentication (prompts for API key if needed)
- Discovers MCP configs across 42+ locations
- Runs a security scan on selected configs
- Identifies which servers can be proxied (skips stdio servers)
- Detects already-proxied servers (no double-proxying)
- Registers servers with the Igris API
- Backs up original configs to
~/.igris/backups/ - Rewrites configs with proxy URLs
status
Show active sessions and recent audit events:
policy list / policy get
View governance policies from the CLI:
proxy uninstall
Restore original MCP configs from a backup:
scan
Scan one or more MCP configuration files.
| Flag | Default | Description |
|---|---|---|
[path] | auto | Path to MCP config file |
--format | table | Output format: table, json, sarif |
--severity | low | Minimum severity to show |
--fail-on | high | Exit code 1 if findings at this level or above |
--verbose | false | Show full details and remediation text |
--no-color | false | Disable ANSI colored output |
--auto | false | Auto-discover all known config locations |
--json-pretty | false | Pretty-print JSON output |
--config | auto | Path to .igrisrc config file |
--disable | — | Comma-separated rule IDs to skip |
--no-banner | false | Suppress upgrade nudge banner |
rules list
List all available detection rules.
rules info
Show details for a specific rule.
Auto-Discovery
When you runigris scan --auto, the CLI checks 42 known config locations across all major MCP clients:
| Client | Config Locations |
|---|---|
| Claude Desktop | ~/.claude/claude_desktop_config.json |
| Claude Code | ~/.claude.json, ~/.claude/settings.json, .mcp.json |
| Cursor | ~/.cursor/mcp.json |
| Windsurf | ~/.config/windsurf/mcp.json, ~/.codeium/windsurf/mcp_config.json |
| VS Code | .vscode/mcp.json, ~/Library/Application Support/Code/User/mcp.json |
| Zed | ~/.zed/settings.json, ~/.config/zed/settings.json |
| Gemini CLI | Gemini-specific config paths |
| Amazon Q | Amazon Q CLI config paths |
| JetBrains | IDE-specific MCP config |
| Others | OpenCode, Amp, Kilo Code, Roo Code, Cline, Augment, Copilot CLI |
| Generic | mcp.json, mcp-config.json |
Output Formats
Table (default)
Color-coded terminal output with a findings table and summary:JSON
Machine-readable output for CI/CD pipelines:SARIF
SARIF 2.1 format for integration with GitHub Code Scanning, Azure DevOps, and other SARIF-compatible tools:Exit Codes
| Code | Meaning |
|---|---|
0 | No findings at or above --fail-on level |
1 | Findings detected at or above --fail-on level |
2 | CLI error (missing file, bad config, unknown rule) |
Configuration File
Create an.igrisrc file in your project root (or any ancestor directory) to set default options:
- CLI flags (
--severity,--disable, etc.) .igrisrcfile- Default values