Register GNO with Amp in one command. The installer records an absolute entrypoint plus the active index, config, data, and model cache, so the client does not depend on shell PATH or exported GNO_* variables to find the right workspace.

Connects via: MCP server
Requires: Bun 1.3+ and one indexed folder
Data boundary: Corpus and index stay on your machine

Install

Connect Amp in one command.

gno mcp install --target amp

gno mcp status

gno mcp install --target amp --dry-run --json

What it unlocks

25 read-only retrieval, graph, and status tools
Capsule build and verification as structured tools
Writes stay behind an explicit opt-in flag

Prove it actually works

A written config file is not a working integration. GNO distinguishes the two, and so should you.

Run gno mcp status to confirm GNO is registered for the target.
Open the Connectors page in gno serve and run the explicit read-only retrieval check. It proves the configured client can actually retrieve, not just that a config file exists.
Ask the client something only your corpus knows. If it answers with a citation into your files, the wiring is real.

Keep reading

Related guides and features.

MCP reference

/docs/mcp

Open

AI tool integration

/features/mcp-integration

Open

Privacy model

/features/privacy-first

Open

All integrations

Every supported client

Browse all