sh

capa sh turns every configured tool into a CLI. MCP tools live under the server id; command tools appear at the top level (or under a custom group). Tool ids are slugified to kebab-case.

Requires a capabilities file in the current project and a running capa server (capa start / after capa install).

Synopsis

capa sh [args...]
capa sh [--raw] <group> <subcommand> [--arg value...]
capa sh [--raw] <command> [--arg value...]

Flags

Flag	Description
--raw	Return raw tool output (skip the formatter). Position-independent — works before or after the command tokens

capa sh does not take a dedicated --json for tool payloads. Global --json only affects machine-readable CLI status from capa itself.

Caution

Older workflows used capa sh --json for tool output. Use capa sh --raw to skip the formatter. Global --json is only for machine-readable CLI status — it does not replace --raw.

Usage patterns

Invocation	Effect
capa sh	List available commands
capa sh <group>	List subcommands for an MCP server group
capa sh <group> <tool> [--args]	Run an MCP tool
capa sh <command> [--args]	Run a top-level command tool
capa sh <unknown> ...	Pass through to the OS shell
capa sh --help / … --help	Contextual help at any level

Examples

capa sh
capa sh gitlab
capa sh gitlab list-merge-requests --help

capa sh gitlab list-merge-requests --project-id 123 --state opened

# Raw tool output (any position)
capa sh --raw gitlab list-merge-requests --project-id 123
capa sh gitlab list-merge-requests --project-id 123 --raw

# Top-level command tool
capa sh find-skills --query "git automation"

# OS passthrough
capa sh git log --oneline

See also

• Server lifecycle
• install
• Global flags
• Tool exposure