What it unlocks
- Project-scoped configuration you can commit alongside the deployment
- One resident runtime serving several chat sessions
- Local corpus, local index, no external vector store
LibreChat + GNO
Self-hosted chat, self-hosted knowledge
LibreChat already keeps your conversations on infrastructure you control. GNO does the same for the documents behind them. Install at project scope and LibreChat gains local retrieval over your corpus without shipping it to a hosted vector database.
- Connects via
- MCP server
- Requires
- Bun 1.3+ and one indexed folder
- Data boundary
- Corpus and index stay on your machine
Install
Connect LibreChat in one command.
gno mcp install --target librechat --scope projectgno mcp statusgno daemon --detachProve it actually works
A written config file is not a working integration. GNO distinguishes the two, and so should you.
- Run
gno mcp statusto confirm GNO is registered for the target. - Open the Connectors page in
gno serveand 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