overwatch start
Start Overwatch with multiple MCP servers from a configuration file.Usage
Options
| Option | Description |
|---|---|
-c, --config <path> | Path to config file (default: auto-detect) |
--fail-mode <mode> | Fail mode: open, closed, readonly (default: closed) |
--no-audit | Disable audit logging |
--approval <method> | Approval method: terminal, webhook |
--approval-webhook-url <url> | Webhook URL for remote approvals |
--approval-webhook-secret <secret> | Secret for HMAC signing webhook payloads |
-t, --timeout <ms> | Approval timeout in milliseconds (default: 60000) |
Examples
Start All Servers
overwatch.yaml.
With Custom Config
Configuration File
Createoverwatch.yaml:
Config File Locations
Overwatch searches for config in this order:- Path specified with
--config overwatch.yamlin current directoryoverwatch.ymlin current directory~/.overwatch/config.yaml
Server Configuration
Each server can have:| Field | Type | Description |
|---|---|---|
command | string | Command to run (required) |
args | string[] | Command arguments |
env | object | Environment variables |
policies | array | Policy rules |
Policy Configuration
Each policy rule can have:| Field | Type | Description |
|---|---|---|
tools | string/string[] | Tool name(s) or pattern (* for all) |
action | string | Action: allow, deny, prompt |
paths | object | Path-based rules (for filesystem) |
Multi-Server Benefits
Running multiple servers throughoverwatch start:
- Single point of security policy management
- Unified audit logging
- Shared session grants across servers
- Tool shadowing detection across servers