~/.continue/mcpServers/*.json for MCP servers (the Claude-Desktop JSON
shape, name-keyed) — so Nika gets its own file and your
comment-bearing config.yaml is never touched. The binary comes first:
brew install supernovae-st/tap/nika
(other paths).
Create ~/.continue/mcpServers/nika.json:
nika wire continue ships in the next release and writes exactly this
file — idempotent, nothing else in your Continue setup touched.
External writes are not hot-reloaded: reload Continue (or re-save
config.yaml) to pick the server up.The repo side
nika init writes the agent-teaching surface (AGENTS.md, rules) plus
the $schema modeline for validation and completion on *.nika.yaml.
Verify
Continue’s tool list shows the ninenika_* tools
(the oracle’s contract: validate, explain, schema,
cost — no execution, no mutation). Then prove the loop end-to-end:
integrate in 10 minutes.