Integrations

Claude Code integration

Use GNO with Claude Code via the SKILL.md install or the MCP server.

Claude Code supports two integration paths. Skills install GNO as a /gno slash command with zero context pollution. MCP exposes the same retrieval tools through the Model Context Protocol so Claude can call them automatically.

Quickstart

bun install -g @gmickel/gno
gno init ~/notes --name notes
gno index

# Install the skill (preferred — zero context overhead)
gno skill install --target claude --scope user

# Optional: also install MCP for automatic tool calls
gno mcp install --target claude-code

The skill target is called claude (Claude Code is the default). Use --scope user to install globally, or omit it for project-local install.

Using the skill

After installing the skill, Claude Code exposes a slash command:

/gno search "authentication patterns"
/gno query "how does our API handle errors"
/gno ask "what's our deployment process"

Skills are preferred for coding agents because they have zero context window overhead — the tool definitions only load when the slash command is invoked. Use gno skill install --target all to install across Claude Code, Codex, OpenCode, and OpenClaw at once.

Using MCP

With the MCP server installed, Claude Code can call GNO tools automatically. Just ask in plain language:

“Search my notes for deployment procedures”

“Find my architecture docs and summarize the relevant parts for this change”

Claude picks the right tool (gno_query, gno_search, etc.) based on the request.

Project scope

For project-specific knowledge, install at the project scope. This writes a .claude/settings.json in the current project instead of the user-level config.

gno mcp install --target claude-code --scope project