command: nika · args: [mcp]. This page is one anchor per client, so
directory listings can deep-link straight to their tool.
For cursor · vscode · windsurf · claude · codex the wiring is one
command (idempotent, writes the right file):
nika init first — the agent-teaching surface
(AGENTS.md, rules, the repo skill) is what makes the oracle useful.
Cursor
nika server into ~/.cursor/mcp.json. The repo side
(.cursor/rules/nika.mdc, auto-attached on *.nika.yaml) comes from
nika init. The VS Code extension also installs into Cursor via OpenVSX.
Claude Code
Codex
VS Code / Copilot
nika init also writes .github/copilot-instructions.md and the
.vscode/settings.json schema mapping (validation + completion in any
YAML-aware editor).
Zed
Settings →context_servers:
Gemini CLI
~/.gemini/settings.json:
Windsurf
OpenCode
NativeAGENTS.md + repo-skill discovery — see the dedicated
OpenCode page.
Hermes
Tap-installable delegation skill +mcp_servers stanza — see the dedicated
Hermes page.
Continue
~/.continue/config.yaml:
Cline
MCP settings (cline_mcp_settings.json):
Aider
Aider reads repo conventions rather than MCP:nika init’s AGENTS.md
covers it (add CONVENTIONS.md: AGENTS.md to .aider.conf.yml if you keep
conventions elsewhere). The check loop is the same:
nika check <file> after every edit.
Verify (any client)
Ask the agent to list its tools — the eightnika_* names should appear.
Then prove the loop end-to-end:
integrate in 10 minutes.
Client config formats move fast. The stable contract is the stanza (nika+mcp) and the oracle’s read-only surface; when a client’s config path changes, only this page’s anchor needs the touch-up.