Yggdrasil
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ygg_healthA | Report the local Yggdrasil memory engine's health: running status, total stored-memory count, and whether semantic (dense-vector) search is available. Call this first when any other ygg_* tool fails unexpectedly, to confirm the engine is up before retrying. Returns a small JSON status object. |
| ygg_recallA | Search durable memory ACROSS ALL projects for prior solutions, decisions, and lessons to reuse. Use BEFORE solving any non-trivial problem ("have I handled this before?"); for one known project use ygg_bootstrap to load its context or ygg_search for a targeted query instead. Ranks by relevance and past usage — lexical by default, semantic when embeddings are enabled. |
| ygg_bootstrapA | Load the top durable memories for ONE project — decisions, conventions, lessons, and open status — to prime work at the start of a task. Use when you already know the project; for cross-project discovery use ygg_recall, for a targeted in-project query use ygg_search. Results are project-scoped and ranked, most-used and pinned first. |
| ygg_searchA | Search ONE project's durable memory with a free-text query and optional type filter — the precise, in-project lookup. Use when you know the project and want specific matches (e.g. every 'fix' about auth); for cross-project discovery use ygg_recall, to load a project's whole context use ygg_bootstrap. Lexical BM25 plus semantic ranking when embeddings are enabled. |
| ygg_rememberA | Persist ONE atomic, reusable fact (a decision, lesson, fix, convention, or status) to a project's durable memory for future sessions. Call right after you decide something, learn a lesson, or fix a non-obvious bug; store one idea per call, phrased to stand alone. Near-duplicates are merged automatically and obvious secrets (API keys, tokens) are refused. Returns the saved memory id. |
| ygg_materializeA | Write ONE stored memory to a human-readable Markdown note (Obsidian-compatible) on disk; the stored memory itself is unchanged. Use when the user wants to read, edit, or archive a specific memory as a file. Needs the memory id from a prior ygg_recall / ygg_search / ygg_bootstrap result plus its project; returns the written file path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The tools are largely distinct: health, remember, and materialize are clearly separate, while recall, bootstrap, and search all retrieve memories but are differentiated by scope (cross-project vs. project context vs. targeted query). Descriptions include explicit guidance on when to use each, reducing but not eliminating the chance of confusion.
All tools share the consistent 'ygg_' prefix and use lowercase snake_case. Most follow a verb-based pattern (recall, bootstrap, search, remember, materialize), though 'ygg_health' is a noun rather than a verb, creating a minor inconsistency.
Six tools is a well-scoped count for a memory server. Each tool earns its place: health monitoring, cross-project recall, project priming, targeted search, memory persistence, and file export. There are no redundant or filler tools.
The server covers create, read/retrieve, and export operations well, but lacks explicit update and delete capabilities for stored memories. Automatic near-duplicate merging partially addresses updates, but there is no clear way to edit or remove a stale or incorrect memory, which is a notable lifecycle gap.