Nexus

A local MCP server that gives Claude a persistent memory, a private search index for your files and chats, encrypted secret storage, cost visibility across every LLM you use, and a bridge to every other MCP server on your machine.

Claude Desktop is powerful, but on its own it forgets everything between chats, can’t see your files, can’t hold API keys safely, can’t tell you what you’ve spent this month, and only talks to one MCP server at a time. Nexus fixes all of that from a single local process.

Status: 1.0 — 342 tests green. All features are opt-in; existing users can enable them one at a time.

---

60-second tour

Without Nexus:

You: “Can you review the auth middleware in my project?” Claude: “Sure — please paste the code.” [You paste 400 lines.] Claude: “I see a race condition in the token refresh… want me to explain?” You: “Yes.” [Answers.]

— next day, new chat —

You: “What did we decide about that auth issue yesterday?” Claude: “I don’t have access to previous conversations.”

With Nexus:

You: “Register ~/code/my-app as workspace app.” Claude: [workspace_register → indexed 340 files in 4s]

You: “Review the auth middleware in workspace app.” Claude: [workspace_search → workspace_read_file src/auth/middleware.ts → returns the actual code and reviews it]

— next day, new chat —

You: “Recall what we decided about the auth issue.” Claude: [recall query="auth middleware review" → surfaces yesterday’s chat] “We agreed to add a mutex around token refresh…”

That’s the whole product in three exchanges. Everything else is variations on the same theme: make Claude aware of the stuff you already have.

---

Who is this for

• Solo developers who use Claude Desktop daily and are tired of pasting code.
• AI/ML engineers running local Ollama alongside cloud APIs and wanting one unified interface.
• Privacy-conscious users who don’t want secrets or notes leaving their machine.
• Anyone paying multiple LLM bills and wanting one number for monthly spend.
• MCP power users who want to compose multiple upstream MCP servers under one roof.

It is not for:

• Teams that need multi-tenant SaaS features (auth, RBAC, sharing).
• Enterprises that need SOC-2 / GDPR audit tooling out of the box.
• Anyone who doesn’t already use Claude Desktop (Nexus is an MCP server — Claude Desktop is its primary client).

---

The problem

Anyone who uses Claude Desktop seriously runs into the same wall:

1. No cross-conversation memory. “What did we decide about the migration last Tuesday?” — Claude has no idea.
2. Every prompt starts from zero. You paste the same code, the same doc, the same context, chat after chat.
3. Secrets end up in chat. An API key pasted once for a quick test now lives in your Claude history, in your exports, in your logs.