Connect your agent¶
CodeNavi speaks MCP over streamable HTTP — one server, one /mcp endpoint, every client. Pick your agent below for the exact config and per-client notes; the guides in this section also cover token auth, tool approvals, and each client's gotchas.
Two shortcuts worth knowing:
- On a running server, open
http://localhost:8765/connect— the built-in wizard renders your client's config with your real token filled in and a live Verify button. Server on another machine? Open it from the client at the server's address (http://<server-ip>:8765/connect) — the snippets follow the address in the browser bar. Server-side bind, firewall and the Claude Code env block: Remote access → Same LAN. - No server yet? The public preview of the same wizard at codenavi.com/connect-preview shows the config for 16 clients with placeholders you fill in.
Client guides¶
-
The bundled plugin: one-command install, 12 slash commands, skills, statusline.
-
Connect via custom connectors — including from another machine on your LAN.
-
Bundled plugin with wrapper commands, or plain
config.tomlMCP wiring. -
Bundled plugin for the IDE and the
agyCLI — see also the Windows guide. -
opencode.jsonMCP config with per-tool permissions. -
Requires the
pi-mcp-adapterextension; config and caveats. -
Native MCP support (agent mode) — the config shape most MCP-capable editors share.
-
Context server config; runs air-gapped with local models.
-
Local-first chat workspace over your CodeNavi index.
-
GitHub / Forgejo Actions — CodeNavi-backed review in your pipeline.
Other MCP clients¶
Cursor, Windsurf/Devin, Cline, Roo Code, Continue, and anything else that speaks MCP connect with the same endpoint and token — the config is a minor variation of the VS Code shape. Grab the exact snippet for your client from the connect-preview picker, or from your own server's /connect wizard.
Exposing the server beyond localhost (HTTPS, reverse proxy, tokens)? See Remote access.