One command registers GNO as a context server for Zed, with an absolute runtime path and pinned workspace roots. Zed's assistant can then search, retrieve, and cite from your local corpus instead of relying on what happens to be open in the editor.

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

Install

Connect Zed in one command.

gno mcp install --target zed

gno mcp status

gno daemon --detach

What it unlocks

Hybrid retrieval as a first-class assistant tool
One warm resident runtime shared with your other clients
Graph traversal and backlinks for connected notes

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

Daemon and resident runtime

/features/daemon-mode

Open

Hybrid search

/features/hybrid-search

Open

All integrations

Every supported client

Browse all