Point GNO at the vault directory and it indexes what is already there: wiki links, frontmatter tags, and nested folders. You get hybrid search that survives paraphrasing, cited answers, a knowledge graph, and an MCP endpoint so your AI tools can read the vault too. Markdown stays editable in both places.

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

Install

Connect Obsidian in one command.

gno setup ~/Documents/Obsidian --name vault

gno mcp install

gno query 'what did we decide about pricing' --collection vault

What it unlocks

Semantic search that finds the note you paraphrased
Cited answers across the whole vault
Wiki links, backlinks, and tags understood natively
Your agent reading the vault over MCP
Vault files stay exactly where they are, in plain Markdown

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.

GNO compared to Obsidian

/comparisons/obsidian

Open

Note linking

/features/note-linking

Open

Knowledge graph

/features/graph-view

Open

All integrations

Every supported client

Browse all