AI & agents
Your own assistant, connected
Your archive shouldn't be trapped behind one assistant. Nolocron speaks the Model Context Protocol, so the AI clients you already use can reach it — within limits you set.
Problem
Why it matters
Memory locked inside one app is just another silo. If your context is valuable, it should be reachable by the tools you choose — without handing over your whole archive.
Capabilities
What Nolocron provides
- An MCP bridge exposes Nolocron to Claude Desktop and other MCP-compatible clients.
- 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 vault-scoped form.
Workflow
How it works
- Generate a bridge token.
- Point your MCP client at Nolocron.
- Search and read your archive from inside that assistant.
- Scope what it can reach with project rules.
Evidence
Product proof points
- Your archive powers tools you already use.
- Access is token-authenticated and scoped, not wide open.
- An open protocol — no proprietary lock-in.
Related