Skip to main content

kapi mcp

kapi mcp

Start an MCP server over stdio.

--tools picks the tool sets it serves, as a comma-separated list:

writing (default) context_read and the context:// resources, context_search, context_note (record what the assistant noticed or a person changed), context_session_summary, check_file, and read_blocks, apply_edits and describe_format, which read a document's blocks, write change sets back with its structure kept, and say what a format supports content check_text, voice_check, voice_rewrite, term-check, detect_format, redact translation translate, up, up_plan, stats review review_queue, review_block, and apply_edits, which records a pre-review all every set

Two flags add what no set holds, for debugging:

--all-tools every CLI-visible registry tool (pipeline steps, format internals, one-off transforms) --all-flows the flow-running verbs --all every set and both of these

Commandmcp
Groupadvanced
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
FlagTypeDefaultDescription
--allboolfalseevery tool set, plus --all-tools and --all-flows
--all-flowsboolfalseexpose the flow-running verbs
--all-toolsboolfalseexpose every CLI-visible registry tool, not the curated set
--project, -pstringpath to a kapi.yaml project recipe or its directory (auto-discovered from cwd if omitted)
--toolsstringSlicetool sets to serve: writing (default), content, translation, review, all
More examples
kapi mcp --tools writing,translationkapi mcp --tools all

← Back to the Command Reference