By mahuebel
Shared Obsidian knowledge vault with git sync, observation capture, and automatic context injection
Find and remove exploratory notes for abandoned or deleted branches
Review and promote exploratory notes to established status after branch merge
Set up a shared knowledge vault (global or per-project) - clone repo, create config, configure MCP server, verify connection
Create a new note in the vault with proper frontmatter and wikilinks
Matches all tools
Hooks run on every tool call, not just specific ones
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A persistent, git-synced knowledge base for dev teams — readable by humans in Obsidian and by AI assistants via MCP.
Lore gives your team a shared vault where architecture decisions, coding conventions, debugging insights, and research findings accumulate over time instead of getting lost between sessions. Notes are written as claims, reviewed like code, and promoted through a lifecycle that mirrors your git workflow.
Per-developer memory tools (claude-mem, auto-memory, .claude/ files) work well for individual context, but they're invisible to the rest of the team. When a new developer joins a session — or the same developer starts a fresh one — the context rebuilding starts over. Lore solves this by making team knowledge a shared, versioned artifact that any editor can read and write through MCP.
Notes follow a git-like lifecycle: exploratory on feature branches, promoted to established on merge, or discarded on branch abandonment. Only validated knowledge reaches main.
lore/
├── vault-mcp/ TypeScript MCP server — portable vault operations
├── vault-sync/ Claude Code plugin — intelligent orchestration layer
└── vault-animation/ Remotion animations for demos
The vault template lives in its own repo: mahuebel/vault-template
A TypeScript MCP server that provides 12 tools for vault operations. Works with any MCP-compatible editor — Claude Code, Cursor, Windsurf, VS Code Copilot, etc.
Tools:
| Category | Tools |
|---|---|
| Config | vault-init |
| CRUD | vault-create-note, vault-read-note, vault-update-note, vault-delete-note |
| Lifecycle | vault-promote, vault-discard |
| Query | vault-query, vault-search |
| Git Sync | vault-pull, vault-push, vault-status |
A Claude Code and Cursor plugin that adds intelligent orchestration on top of vault-mcp:
/vault-note, /promote-to-vault, /vault-cleanup, and a setup wizardRemotion-based animations for project demos and documentation.
Go to mahuebel/vault-template and click "Use this template" to create your team's vault repo. Then clone it locally:
git clone [email protected]:your-org/your-vault.git ~/obsidian/team-vault
No build step required — the server runs via npx:
Claude Code:
claude mcp add --scope user \
--env VAULT_PATH=/path/to/your/team-vault \
--env VAULT_AUTHOR=your-github-username \
-- vault-mcp npx lore-vault-mcp
Cursor — add to .cursor/mcp.json:
{
"mcpServers": {
"vault-mcp": {
"command": "npx",
"args": ["lore-vault-mcp"],
"env": {
"VAULT_PATH": "/path/to/your/team-vault",
"VAULT_AUTHOR": "your-github-username"
}
}
}
}
Restart your editor after adding.
Call the vault-init MCP tool (or use /vault-setup if you installed the plugin):
vault-init --vault_path ~/obsidian/team-vault --author your-github-username
This adds skills, hooks, and the promoter agent. See Editor Compatibility for install instructions per editor.
Open your vault folder as an Obsidian vault for visual browsing, graph view, and manual editing.
By default, Lore uses a single global vault at ~/.lore/vault/. This works well for teams working on related products that share conventions and architecture knowledge. But if you work across unrelated projects — or as a freelancer switching between clients — you may want a separate vault per repository.
Run the setup wizard in any project:
/vault-setup --project
This creates a .lore/config.json in your project root with your vault configuration.
The .lore/config.json file:
Spec-driven design system: visual brainstorming with forge, structured plans with SDD defaults, subagent/agent-team execution with TDD and worktree hygiene
Visual workspace for iterating on UI with Claude Code — point, comment, react, and refine in real time instead of describing changes in prose
mahuebelnpx claudepluginhub mahuebel/lore --plugin vault-syncPersistent Obsidian-based memory for coding agents. Automatically orients from a knowledge vault at session start, navigates project architecture via graph traversal, and writes discoveries back to the vault.
AdamTylerLynchBidirectional knowledge flow between Claude Code and Obsidian — 20 MCP tools, skills, and hooks for PKM
AdrianV101Create and edit Obsidian vault files including Markdown, Bases, and Canvas. Use when working with .md, .base, or .canvas files in an Obsidian vault.
breferrariSecond Brain automation for Obsidian vaults — entity management, ingestion, compression, and sync via Claude Code skills
iurykriegerManage an Obsidian vault as your development knowledge base and automatic work journal. Auto-captures commits, tasks, and Claude Code components with structured frontmatter.
mwguerraA self-developing knowledge management system for Claude Code. Bridges AI memory to an Obsidian vault with feature-organized spine notes, auto-capture skills, and color-coded graph visualization.
Nodewarrior