whimsicality-mcp
Official# whimsicality-mcp (deprecated)
**This package is superseded by [`whimsicality-db`](https://www.npmjs.com/package/whimsicality-db).**
`whimsicality-db` is a strict superset of this server, built on SQLite + FTS5 instead of JSON files and hand-rolled BM25. It adds session tracking, event logging, todo management, and a tagged context index — all backed by SQLite's WAL mode for concurrent readers and native FTS5 for search.
## Migration
Install `whimsicality-db` and use the `db_import` tool to import your existing `whimsicality-mcp` data:
```json
{
"mcpServers": {
"whimsicality-db": {
"command": "npx",
"args": ["whimsicality-db"]
}
}
}
```
Then call `db_import` with the path to your old storage directory:
```
db_import({ source_dir: "~/.whimsicality/mcp-storage" })
```
Your memory entries, documents, and cache chunks will be imported into the SQLite database. After verifying, you can remove the old storage directory.
## Why the switch?
This server used a JSON file for memory and docs, with a hand-rolled lockfile protocol, atomic-rename discipline, byte-bounded LRU, garbage collector, and BM25 implementation. SQLite gives you WAL, transactions, page cache, no orphans, and a battle-tested BM25 for free. The result is faster, more reliable, and scales to millions of entries instead of thousands.
## License
MIT
TDQS
Scored across 14 tools
Most tools have distinct purposes: facts, context slots, RAG search, plans, snippets, and compaction each serve different needs. However, facts and context both act as persistent key-value stores, which could cause some confusion, though the descriptions clarify context as memory and facts as factual data.
The naming follows a consistent pattern of 'whim_<resource>_<action>' for most tools (e.g., whim_facts_get, whim_context_set, whim_rag_search). Minor exceptions include whim_compact, which lacks a resource category, and slight verb placement variations, but overall the pattern is predictable.
14 tools is a reasonable count for a multi-purpose memory and utility server. Each tool covers a distinct functional area, though some areas like facts and context could potentially be merged, but the count is within the well-scoped range and does not feel excessive.
The server covers core operations for facts, context, and RAG, but has notable gaps: no delete for facts, plans, or snippets; no list for plans or snippets; and no way to retrieve a snippet by name (only search). These missing operations may force agents to work around or leave orphaned data.