Surfaces
Point your own AI app straight at it
Your archive shouldn't be trapped behind one assistant. Nolocron speaks the Model Context Protocol, so the AI app you already use can reach your knowledge as a permissioned source — within the limits you set.
Available
How the connection works
Your AI app
Claude, Cursor & friends
The chat app you already use, asking in plain language.
The governed gate
The MCP bridge
A small, controlled toolset — not a backdoor to everything.
- search & read
- list & scope projects
- your whole archive
Your vault
Local, on your disk
Your archive in open formats — it never leaves your machine.
01
Why it matters
Memory locked inside one app is just another silo. If your context is valuable, the tools you choose should be able to reach it — without you handing over the whole archive.
02
What Nolocron provides
- An MCP bridge exposes Nolocron to Claude Desktop and other MCP-compatible apps.
- A focused tool set: search, read a resource, list and create projects, set scope rules.
- Token authentication, per-session rate limiting, and a local transport.
- Resources addressed by stable nolocron:// URIs, including a vault-scoped form.
03
How it works
- Generate a bridge token.
- Point your MCP app at Nolocron.
- Search and read your archive from inside that app.
- Scope what it can reach with project rules.
04
Proof
- Your archive powers the tools you already use.
- Access is token-authenticated and scoped — read, search, and project setup, never the tools that change your data.
- An open protocol — no proprietary lock-in.
Related