Skip to content
SHC Docs

shc mcp serve

shc mcp serve

Section titled “shc mcp serve”

serve MCP over stdio, wrapping the daemon API

Synopsis

Section titled “Synopsis”

Run an MCP server on stdin/stdout for a local agent (Claude Code, an IDE, any MCP client). Tools are thin wrappers over the daemon API — the daemon’s own authorization and tenancy scoping apply to every call. Authentication is ambient, exactly like every other CLI verb: the local unix socket when on-box, the shc auth login stored bearer when remote. Requires the mcp entitlement (any paid tier, or the 30-day trial). Diagnostics go to stderr; stdout carries the protocol.

shc mcp serve [flags]

Options

Section titled “Options”
  -h, --help        help for serve
      --read-only   expose only the read tools (search, status, logs, lists) — first-run safety for untrusted agents

Options inherited from parent commands

Section titled “Options inherited from parent commands”
      --config stringArray   extra YAML config file to layer on top of auto-discovered config; repeatable, later files win
  -d, --debug                enable debug mode (default: $SHC_DEBUG)
  -e, --environment string   environment name (default: $SHC_ENVIRONMENT)
      --exclude string       comma-separated dotted paths to drop
      --fields string        comma-separated columns/keys to show (and their order)
      --filter string        comma-separated dotted paths to keep (drops everything else)
  -o, --output string        output format: tty|text|json|yaml (default: $SHC_OUTPUT)
  -s, --stack string         stack name (default: $SHC_STACK)
  -t, --tenant string        tenant name (default: $SHC_TENANT)
  -v, --verbose              verbose output (default: $SHC_VERBOSE)

SEE ALSO

Section titled “SEE ALSO”
  • shc mcp - serve the SHC API to AI agents over MCP