Knownbase
an MCP server for persistent AI agent memory
Last checked:
What is Knownbase?
Knownbase is a persistent project memory system that gives AI coding agents searchable knowledge about codebase architecture, decisions, debugging discoveries, and constraints. It works with Claude Code, Codex, Cursor, ChatGPT, and any MCP-compatible agent, allowing knowledge to survive sessions and be shared across tools rather than being re-explained or re-derived each time.
Knownbase pricing
Pricing model: Freemium
Free plan, no card required
Knownbase pros
- Knowledge persists across sessions and is shared across multiple AI tools in one workspace
- On-demand retrieval means only relevant information enters the context, avoiding the growing instruction file problem
- Captures reasoning behind decisions and debugging discoveries that version control doesn't preserve
- Integrates via MCP with any compatible agent, preventing context rebuilding when switching tools
Knownbase cons
- Requires agents to actually write and structure knowledge for it to be useful
- Depends on proper prompting and workflow adoption by users and teams
- Limited detail provided on scalability limits, storage constraints, or collaborative features
Frequently asked questions about Knownbase
How is Knownbase different from CLAUDE.md?
CLAUDE.md holds standing instructions written manually, loaded entirely into every session. Knownbase holds accumulated knowledge written by agents, searched on-demand so only relevant slices enter context. Knownbase grows without bound while CLAUDE.md's usefulness depends on staying short.
What can agents store in Knownbase?
Architecture decisions, debugging discoveries, rejected approaches, operational constraints, project conventions, and session handoffs—essentially the reasoning behind decisions that git and instruction files don't capture.
Which AI tools does Knownbase work with?
Claude Code, Codex, Cursor, ChatGPT, and any MCP-compatible agent through the Knownbase MCP server.
Does knowledge survive when I end a conversation?
Yes, knowledge lives outside the context window in Knownbase, so ending a session doesn't end what the project knows.