A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
22 ★ · VonderVuflya/Yggdrasil · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 22 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository VonderVuflya/Yggdrasil;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Stop re-explaining your project to every new AI session. One local memory for Claude Code, Codex, and every MCP agent — shared across sessions, tools, and projects. Zero dependencies. Nothing leaves your machine. Install · How it works · Numbers · Compare · FAQ Read this in: Русский · 简体中文 · Español · Français · 日本語 · Deutsch --- Every new chat, your AI forgets. You re-explain the project, the decisions, the gotchas — every time, in every tool. **Yggdrasil is a tiny always-on memory that any agent plugs into.** Open a new session, in any project, with any AI, and it already knows what you decided, what broke, and what's still open. No "let me remind you what we did yesterday." It's just there. 🚀 Install Two commands, inside **Claude Code** (the plugin launches via uv): The engine lazy-starts on first use and generates its own local token — no API key, no cloud, nothing to configure. Codex and Cursor use the same flow. All other channels — CLI daemon, Homebrew, npm, Claude Desktop, from source… | Host / tool | Command | | --- | --- | | **uvx** _(recommended CLI)_ | uvx --from yggdrasil-memory ygg install | | **npm / npx** | npx yggdrasil-memory install | | **pipx** | pipx install yggdrasil-memory && ygg install | | **pip** | pip install yggdrasil-memory && ygg install | | **Homebrew** _(macOS)_ | brew install VonderVuflya/tap/yggdrasil && ygg install | | **Claude Desktop** _(app)_ | drag the .mcpb from the latest release onto Settings → Extensions, paste your token (ygg token) — the desktop app then shares the same memory as your CLI agents (guide) | | **from source** | uvx --from git+https://github.com/VonderVuflya/yggdrasil.git ygg install | ygg install is a one-time guided setup: it installs an always-on background service, registers the MCP tools with every agent host it finds — **Claude Code, Codex, OpenCode** — and, if your hardware allows, recommends optional local models (or pick none to stay zero-config). OpenCode — nothing to configure Install OpenCode first, then run ygg install (or ygg redeploy if Yggdrasil is already set up) — the entry is written for you and merged into any existing opencode.json. Confirm with: Installed OpenCode *after* Yggdrasil? Just re-run ygg install. If you'd rather write it by hand, note that OpenCode's schema differs from Claude's in four places at once — servers live under mcp (not mcpServers), type is required, command is one array (not command + args), and env is environment (not env), so the Claude snippet won't port: No token goes in the config — the engine reads the 0600 ~/.yggdrasil/token itself. Run ygg doctor if the tools don't show up. There is also a yggdrasil-memory skill for any Claude surface: MCP connects the *tools*, the skill teaches the agent *when* to use them. Use both for the best behavior. Try it with nothing installed and a throwaway DB: uvx --from yggdrasil-memory ygg serve --reset --db /tmp/ygg.sqlite. Then just work: ask your agent *"recall what we decided about this project"*, tell it *"remember this decision"* — next session it's already there. Verify the install any time with ygg doctor. **Already have history?** Seed memory from your existing Claude Code + Codex transcripts, Obsidian vaults, and CLAUDE.md repos — distilled locally: **Leaving another memory tool?** ygg import --from mcp-memory --path memory.json pulls its whole store into Yggdrasil (deduped, secret-guarded) — then you can delete it. Why - 🧠 **Persistent** — decisions, lessons, and project status survive across sessions. - 🔌 **One brain, every tool** — Claude Code, Codex, OpenCode, and any MCP host share the same memory. - 🌐 **Cross-project recall** — *"this looks like what you did in project B — reuse it?"* - 🧹 **Curated, not captured** — your agent saves the few things that matter; governance dedupes and archives, never deletes. - 🌱 **Self-maintaining** *(opt-in)* — a small local model consolidates memory in the background. Zero API tokens. - 🪪 **One identity everywhere** — an optional name and persona every agent picks up, so Claude Code and Codex feel like the same assistant. - 🔒 **100% local** — your memory lives on your machine. No cloud, no account, no telemetry. 🧠 How it works Yggdrasil is **memory + tools** — the *intelligence* is your LLM. It just makes sure the right memory is in front of the right agent at the right moment.