Kyrzin/kybase

Kybase gives Claude, Cursor, Windsurf and any other MCP-speaking agent a
long-term memory you own: one Markdown knowledge base, running on your own
machine, that every agent can search, read and update — and that you can
open in a browser and edit by hand.
**Self-hosted. Private by default. Plain Markdown. Yours.**
**The problem · Quick start · Connect your agent · What you get · Settings · Sharing · Backups · Upgrading**
The problem
You tell your agent how the staging deploy works. It helps, and the
session ends.
Tomorrow you open a new one:
> **You:** what did we decide about the staging database?
>
> **Agent:** I don't have that context — could you tell me again?
So you explain it again. Then you switch editors, and explain it there too.
With Kybase, the knowledge lives outside the agent:
> **You:** what did we decide about the staging database?
>
> **Agent:** *(searches Kybase)* You moved staging to its own Postgres
> instance so migrations could be tested against real data first — that's
> in "Staging environment", under "Database".
New session, same memory. Different tool, same memory.
Quick start
One local agent
Nothing to install, no Docker, no database to run:
Put that in your client's MCP config and restart it. Your notes live under
~/.kybase, and kybase-mcp export vault.zip gets them back out as plain
Markdown at any time.
The full app
For the web UI, the graph view, share links, and several agents against one
knowledge base:
**macOS and Linux**
**Windows (PowerShell)** — no openssl or sed there, so the secrets are
generated by .NET instead:
Either block generates the only two secrets you need and starts the stack.
Open http://localhost:3000, log in with your KYBASE_SECRET — grep
KYBASE_SECRET .env shows it, or Select-String KYBASE_SECRET .env on
Windows — then connect an agent.
That installs the app and its database — around 1 GB. Notes and text search
work right away.
**Semantic search needs an embedding provider.** Open Settings and pick one:
- **Google or OpenAI** — paste an API key and you are done.
- **Ollama, on your own machine** — start it once, then pick a model in
Settings:
It is not in the default install because its image carries NVIDIA and AMD
GPU runtimes whatever your hardware is — about 4 GB that someone using a
cloud provider would never run. Starting it later touches nothing else:
the app keeps running and no note is affected.
Connect your agent
Kybase speaks MCP over Streamable HTTP at /api/mcp. A client that supports
OAuth signs in once in your browser and gets its own token — listed under
Settings → **Access** and revocable on its own — so your KYBASE_SECRET
never goes into its config.
**Claude Code** — add it once for all your projects:
Then run /mcp in Claude Code, pick kybase → **Authenticate**, and enter
your KYBASE_SECRET on the page that opens.
That's it — the agent can now search your notes, read them, write new ones,
update existing ones and link them together.
Other clients — Claude Desktop, claude.ai, Cursor, Windsurf
**Claude Desktop and claude.ai** — Customize → Connectors → Add custom
connector, same URL, then **Connect** and sign in. Claude connects from
Anthropic's servers, so the instance has to be reachable over HTTPS from the
internet. In Claude Desktop, remote servers go here, not in
claude_desktop_config.json.
**Cursor** — ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
Then connect kybase under Customize → MCPs and sign in.