Server lifecycle
The local capa server (default around localhost:5912) handles credentials, MCP proxying, and capa sh tool execution. capa install usually starts it for you; use these commands to manage it explicitly.
Synopsis
Section titled “Synopsis”capa start [-f|--foreground]capa stopcapa restartcapa statusCommands and flags
Section titled “Commands and flags”| Command | Flags | Description |
|---|---|---|
start | -f, --foreground | Start the server in the background, or in the foreground for debugging |
stop | — | Stop the capa server and any active capa wrap sessions |
restart | — | Restart the capa server |
status | — | Check server health and uptime |
Examples
Section titled “Examples”capa startcapa start -fcapa statuscapa restartcapa stopAfter changing server commands, env vars, or options.toolExposure, restart so the proxy picks up the new config:
capa installcapa restart