fable MCP server
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 |
|---|---|
| fable_searchA | RECALL EARLIER CONVERSATION. Use this WHENEVER you need context that may be outside your window — after a compaction, deep in a long session, or to recall a past decision / discussion across ANY session. PREFER IT over guessing or trusting a compaction summary (the summary is lossy; this is the exact archive). Returns ranked threads with ids, turn/token counts, card titles, decisions and outcomes; then call fable_thread to read one verbatim. |
| fable_threadA | Read one conversation thread VERBATIM (user → assistant → tool turns, in order) under a token budget — the exact past turns, not a paraphrase. Use after fable_search (or with a known prompt_id) to recover precise detail a summary would have lost. Bulky tool results are elided with block pointers (fetch via fable_block). |
| fable_blockA | One transcript record by uuid, byte-identical — the exact original bytes. Use to recover a specific tool result or turn that a summary or thread view elided. |
| fable_pruneA | Slim a session transcript NOW (tool noise, images, bloat) with a vault backup sealed first — nothing is lost, everything stays recallable. Use when the user asks to prune/slim a session or complains about context size. After pruning the CURRENT session, tell the user to /exit and run the returned resume command to load the slim version. |
| fable_rememberA | Store a durable fact the user wants remembered across all future sessions (auto-injected at session start). Use when the user says 'remember that...' or states a lasting preference/decision. |
| fable_contextB | Auto-assemble a paste-ready context pack for a task: searches the archive, picks the strongest threads, splits the budget across them. Returns one sentinel-wrapped block. |
| fable_recallA | Read the durable facts the user stored via /remember (the READ side of fable_remember) — lasting preferences, decisions and constraints, the same ones auto-injected at session start. Call to re-check what the user has committed to before assuming. Optionally scope to a project. |
| fable_filesA | List the files Claude has edited — across the whole archive, or within one session — with edit/write counts and last-touched time. Use to DISCOVER what a past session changed before pulling a file's history. Filter by a path substring or a session id. |
| fable_file_historyA | EVERY version of a file Claude ever edited, reconstructed from the transcript — each version's index, timestamp, tool, session and fidelity (exact replay vs rebuilt-backward). Use to see how a file evolved, or to find the two version indices to diff. Pass a file path (or a distinctive substring of it). |
| fable_file_diffA | Unified diff between any two reconstructed versions of a file (version indices from fable_file_history) — recover exactly what changed between two past edits, or between a past version and the latest. Pass the file path and the two version indices a and b. |
| fable_tagsA | DISCOVER the taxonomy tags fable assigns to threads, for precise tag-filtered recall. Call with NO args to list the tag FAMILIES (domain, activity, topic, technology, pattern, intent, outcome, decision…) with counts; call with family='' to list THAT family's values. Then pass tag='family:value' to fable_search to scope recall to exactly that kind of work — progressive disclosure, so you never need the whole taxonomy up front. |
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 11 tools
Each tool targets a distinct operation: block retrieval, context assembly, file diff/history, file listing, session pruning, fact storage/recall, search, tag discovery, and thread reading. There is no overlap between these functions.
All tools follow the 'fable_<function>' pattern with snake_case. The naming is uniform and predictable, making it easy for an agent to infer the tool's purpose from its name.
With 11 tools, the server covers a complex domain—conversation and file history recall—without being overwhelming. Each tool serves a clear role, and the count feels justified.
The tool set covers the main workflows: storing/recalling facts, searching threads, managing file history, and pruning sessions. Minor gaps include the lack of a tool to update or delete remembered facts, but the core functionality is well-covered.