Integrations
Your tools, reading your files.
GNO installs into ten clients automatically and works with any other MCP client through manual configuration. Each install pins an absolute runtime path plus the active index, config, data, and model cache, so a desktop app opens the same workspace as your shell without inheriting environment variables it never sees. Read-only by default: the fifteen mutating tools require an explicit flag.
The short version
Two ways in: an agent skill or an MCP server.
Skills are lighter and suit coding agents that already shell out. MCP exposes structured tools, including Context Capsule build and verification, Knowledge Delta, and the opt-in verified Ask.
# Coding agents: Claude Code, Codex, OpenCode, OpenClaw
gno skill install --scope user# MCP clients: Claude Desktop, Cursor, Zed, Windsurf, Amp, LM Studio, LibreChat
gno mcp install --target cursor# Inspect exactly what would be written, without writing it
gno mcp install --target cursor --dry-run --jsonClaude Code
Give Claude Code a memory that outlives the session
Claude Desktop
Ask Claude Desktop about your own files
Cursor
Your editor's assistant, reading your actual documentation
Codex
Codex, with your documentation in reach
Zed
Local retrieval inside Zed's assistant
Windsurf
Windsurf plus your own reference material
OpenCode
OpenCode with retrieval that does not bloat the prompt
Amp
Amp, connected to your local corpus
LM Studio
A fully local stack: LM Studio for generation, GNO for evidence
LibreChat
Self-hosted chat, self-hosted knowledge
OpenClaw
OpenClaw with a searchable long-term memory
Obsidian
Keep the vault. Add retrieval your agent can use
Anything else
Any MCP client works, it just needs manual configuration.
Raycast and other compatible clients point at the same stdio or Streamable HTTP endpoint. The MCP reference has the exact command, arguments, and workspace values to copy.