kapi mcp
kapi mcpStart an MCP server over stdio.
The default surface is deliberately small: retrieving the project's context, checking content against it, writing edits back, and running the loop. That is what an assistant needs to work inside this project's context.
Everything else the tool registry can do is still reachable — pipeline steps, format internals, one-off transforms — but as an explicit opt-in, because a surface nobody chose is how it grew to fifty-one tools.
--all-tools every CLI-visible registry tool --all-flows the flow-running verbs --all both
Watch it
mcp needs network access, an API key, or local system access, so it can’t run in the browser playground.See the guides for a recorded run, or try it locally with the installed CLI.
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
| --all | bool | false | shorthand for --all-tools --all-flows |
| --all-flows | bool | false | expose the flow-running verbs |
| --all-tools | bool | false | expose every CLI-visible registry tool, not the curated set |
← Back to the Command Reference