MindBase MCP
Personal Markdown wiki on your disk: the agent reads your sources, merges them into context.md and writes only after you approve.
- 137 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Writes and rebuilds Markdown files in the data folder, with edits made after your approval.
- In cloud mode note text goes to the model provider you choose.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mindbaseDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Writes and rebuilds Markdown files in the data folder, with edits made after your approval.
- In cloud mode note text goes to the model provider you choose.
This is third-party code. Review the repository files before installing.
What it does
MindBase keeps knowledge in plain Markdown files under `~/mindbase-data/`. The agent reads articles, PDFs and notes, discusses takeaways, shows a checkbox plan of edits and writes only what you approve. It never rewrites the original notes in `sources/`. You connect to the wiki through the `mindbase-mcp` MCP server (49 tools) or a Claude Code plugin with 12 slash commands such as `/mb:contribute`, `/mb:build`, `/mb:ask` and `/mb:lint`. `/mb:lint` rereads the whole wiki and reports contradictions with exact quotes. A browser interface with free local models through Ollama is included.
Who it is for. Researchers and note-takers who want a wiki that accumulates knowledge across sessions and stays as plain files.
Good fit when
- You are working through a dozen articles on a topic and want one `context.md` summary.
- The agent has to remember your conclusions in the next session.
- You want the wiki checked for stale claims and orphan pages.
- Your notes live in Obsidian and must stay plain files.
Not a fit when
- You need vector-database search with no text edits.
- Notes are shared by a team editing at the same time.
- Writing to the wiki without confirmation is acceptable for you.
Example request
Add this arXiv paper to mindbase, show the takeaways and an edit plan, and write only what I tick.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
MINDBASE_DATA_DIR- Data folder used instead of `~/mindbase-data/`.
Limitations
The project is in early access and may change. Browser mode needs a local model: the README names `llama3.2:3b` for 8 GB of memory and `qwen3:14b` for 24 GB or more. Slash commands work only in Claude Code; in Cursor and Windsurf you route requests in plain text. The last commit is dated 16 October 2026. Cloud models need your own keys, while local mode works without them. In Cursor, Windsurf and Cline it is worth adding routing rules to the editor rules file; otherwise the model sometimes skips the right tool.
How to disable. Remove the `mb` plugin and the `mindbase` entry from your MCP configuration. Delete `~/mindbase-data/` separately; it holds your notes.
FAQ
How do I install MindBase in Claude Code?
Run `/plugin marketplace add frankchu91/mindbase-llm-wiki`, then `/plugin install mb@mindbase`. After a restart the command list includes `/mb:contribute`, `/mb:build`, `/mb:ask` and `/mb:lint`.
Where is the data stored?
In `~/mindbase-data/`; change the path with `MINDBASE_DATA_DIR`. It is plain Markdown with no private database, so it can live in git.
Is an API key required?
No. The setup wizard picks a free local Ollama model for your memory size, and cloud keys are optional.
How is it different from RAG?
The wiki is written ahead of time and stays on disk. Answers come from the finished synthesis instead of being rebuilt from raw sources on each query.
Which editors are supported?
Claude Code (plugin with slash commands), Cursor, Windsurf, Cline and Continue.dev through `npx -y mindbase-mcp`. Any other MCP client uses the same command.
Discussion
No questions or reviews yet.
Related
MCP serversA personal wiki in a .wiki folder: the agent reads sources, writes cross-linked pages and health-checks the knowledge base
An Obsidian vault template where an agent follows a CLAUDE.md schema to compile sources into a linked wiki and extend it.
A CLI that creates an Obsidian-ready Markdown vault and installs four skills so an agent maintains the knowledge base.
LLM Wiki Manager keeps a personal Markdown wiki through an agent: it ingests sources, links pages and answers with citations
CLI for a personal Markdown knowledge base: the agent writes, searches and lints pages with wiki commands; the tool calls no model
A plugin that turns PDFs, articles and notes into a shared markdown wiki that agents search, cite and keep growing
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| MindBase (this card) | no | not required | 137 | |
| LLM Wiki Compiler | no | 2,254 | compiles a wiki from source material; MindBase keeps a personal wiki with an edit plan and approval of each write | |
| LLM Wiki Skill | no | 155 | only reads a desktop app's knowledge base; MindBase also grows the wiki itself |
README in short
Three layers on disk: sources you control, a wiki the agent edits with approval, and derived indexes and snapshots. Three operations: ingest, build and lint.