Enzyme MCP server
io.github.byenzyme/enzyme·v0.13.2·87 starsSemantic search and pattern discovery for Obsidian and markdown vaults.
not scanned yet
87 stars
Reviews
Write oneNobody has reviewed Enzyme yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Enzyme tools
No tool declarations could be read from the package source. They show once the server is installed.
How Enzyme compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 65% of 1,299 Productivity servers
- GitHub stars
- 87
- more than 91% of 854 Productivity servers
Release history: 9 versions in the registry since 2026-08-28, latest 2026-10-26, typically one every 6 days.
Install Enzyme in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Enzyme repository's README, as published. We do not edit it. Read it on GitHub
🧬 Enzyme
Enzyme introduces a compile step for your Markdown wiki that:
- Uses temporally grounded context sampling that captures the contextual use of tags and wikilinks, or natural accumulation in folders (i.e. pseudo-Zettelkasten)
- With this context, generate questions (called catalysts) and embed them as semantic routes to the whole knowledge base
- Keeps refreshing, but separates new doc ingestion (local, fast) from catalyst evolution (cheap, periodic)
When your agent passes queries through the catalysts, it gets a more personalized way to get caught up on the knowledge base.
New: Enzyme relies on a program that Jev generates through a deterministic scan:
profile relationships {
seek "what matters between people"
notice ["meaningful exchanges", "shared interests", "unfinished conversations"]
}
vault "~/notes" {
question budget 40
sample across time
favor recent periods
learn questions from folder "people"
including linked pages
about relationships
learn questions from folder "meetings" about operational
learn questions from tags ["founding", "ai-ux"] about decisions
learn questions from folder "inbox"
project questions into "~/notes/Readwise"
// Guidance compiled for your agent, not an enforced hook.
when asked {
"Use grep for names, titles, and exact phrases."
retrieve passages through learned questions
answer with sources
}
}Get started
Open your Markdown notes folder in an agent that can run terminal commands, such as Claude Code or Codex, and paste this prompt. If your agent is open elsewhere, replace the first sentence with the path to your notes.
Set up Enzyme for the Markdown notes folder I have open. If you cannot identify it, ask me for its path.
Install Enzyme if needed using https://raw.githubusercontent.com/byenzyme/enzyme/main/install.sh, and install the instructions for this agent. Read and follow the installed enzyme-workspace-setup skill.
You may use Enzyme's online service to suggest settings from my notes and prepare search. Show me what you propose to include or exclude, and let me correct it before building the local search index.
Then answer one useful question using my notes, with links to the sources, and suggest a question I can ask next. Keep my existing notes in place and unchanged. Ask separately before any cleanup, model download, or recurring task.The agent installs Enzyme, reviews the settings with you, and demonstrates an answer from your own notes. You can keep writing and organizing your notes as you already do; cleanup is not a prerequisite.
Terminal setup
If you prefer to install it yourself:
curl -fsSL https://raw.githubusercontent.com/byenzyme/enzyme/main/install.sh | bash
cd /path/to/your/notes
enzyme install claude # or: codex, hermes, openclawThen use the prompt above. For setup without an agent:
enzyme compile -v
# Review the .enzyme settings file at the path printed by compile.
enzyme init --quiet
enzyme doctor
enzyme petri --query "a question about your notes"
enzyme catalyze "a question about your notes"compile uses online selection and saves proposed settings under ~/.enzyme/configs/. Review that file before init builds the local index.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Enzyme: common questions
- Is Enzyme MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Enzyme safety report
- Does Enzyme need an API key?
- No secret keys are declared. It reads 4 settings from the environment.
- Is Enzyme maintained?
- The last commit was 28 days ago (2026-10-07). The latest release is v0.13.2.
- What can I use instead of Enzyme?
- Servers from other publishers that do the same job: Obsidian Hybrid Search MCP server, Obsidian Turbocharged MCP server and Exomem MCP server. Compare all Enzyme alternatives.
- How does Enzyme compare with other Productivity MCP servers?
- safety score 85/100 (higher than 65% of 1,299 Productivity servers); github stars 87 (more than 91% of 854 Productivity servers). Full comparison.
Alternatives to Enzyme
Same job from other publishers: the closest match first, then the best rated.
- Obsidian Hybrid SearchSearch Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval.not reviewedEstablishedB
- Obsidian TurbochargedGoverned Obsidian vault access: hybrid retrieval, Markdown-native memory, HITL confirmations.not reviewedGrowingB
ExomemLocal Markdown/Obsidian knowledge substrate for MCP agents with governed memory and hybrid search.not reviewedEstablishedA- SeekstoneFilesystem-direct Obsidian MCP server — search and edit your vault with low context-tax.not reviewedGrowingA
- Obsidian Vault MCPLocal Zotero, MinerU, Obsidian literature workflow with transactional Analysis notes.not reviewedGrowingA