fortytwo-guide
A semantic-memory MCP server that stores text 'memories' with provenance and enables recall by meaning (vector search), keyword (FTS5), or structured filters.
README
@justfortytwo/guide
A standalone semantic-memory MCP server. It stores text "memories" with
free-form provenance and recalls them by meaning (vector search), by keyword
(FTS5), or by structured filter. Backed by SQLite + sqlite-vec, embeddings
from a local Ollama model.
It is Ford-agnostic: no journal/persona/approval coupling, just a generic memory store and tool surface. It can be used on its own, or as a Claude Code plugin.
What it stores
A memory is content plus provenance:
| field | meaning |
|---|---|
content |
the text (embedded for recall) |
source |
where it came from — free-form (owner, web, tool:foo) |
observed |
how it was observed — free-form (stated, inferred, imported) |
date |
ISO date the memory pertains to (defaults to today, UTC) |
tags |
free-form tags for filtering |
supersedes |
id of a prior memory this one replaces (history is kept) |
Recall is hybrid: recall (semantic), lexical (FTS5 keyword), and query
(structured). reindex + recall_docs index/search a directory of markdown
documents separately from the memory store.
MCP tools
The server registers under the id fortytwo-guide, so a consumer calls the
tools as mcp__fortytwo-guide__<tool>:
| tool | description |
|---|---|
store |
store a memory (+ provenance); set supersedes to replace one |
query |
structured query (source/observed/tag/time; live rows by default) |
recall |
semantic top-k recall by meaning |
recall_docs |
semantic recall over reindexed markdown |
lexical |
full-text keyword search (FTS5) |
reindex |
self-heal the doc index from a markdown directory |
export_range |
render a date range of memories to markdown |
Contract version
Consumers depend on the tool surface, not the internals. The contract is versioned:
import { GUIDE_TOOL_CONTRACT_VERSION, guideToolContract } from '@justfortytwo/guide/contract';
- A major change to a tool name, its required inputs, or its result shape is
a contract break → bump
GUIDE_TOOL_CONTRACT_VERSION. Siblings pin a caret range on@justfortytwo/guide, so a major bump forces an explicit opt-in. - Additive changes (new optional inputs, new tools) do not bump it.
guideToolContract is the authoritative human-readable list of tools and their
guarantees, kept in sync with the wire schema in src/tools.ts.
Embedder
The default embedder is OllamaEmbedder, which calls a local Ollama
/api/embeddings endpoint.
OLLAMA_BASE_URL=http://localhost:11434 # default
EMBED_MODEL=qwen3-embedding:0.6b # default model (1024-dim)
Pull the model once:
ollama pull qwen3-embedding:0.6b
If EMBED_MODEL is unset, the server falls back to a deterministic,
dependency-free FakeEmbedder — useful for tests, CI, and first-run smoke
checks with zero infra. (The vector tables are fixed at 1024-dim; a model with a
different dimensionality requires a schema change.)
Standalone usage
# build (once); the server runs the built JS, not TS
npm run build
# apply migrations to the DB (DB_PATH or ./memory.db)
DB_PATH=./memory.db npm run migrate
# run the MCP server over stdio
DB_PATH=./memory.db EMBED_MODEL=qwen3-embedding:0.6b fortytwo-guide
The bin is fortytwo-guide → dist/index.js. You can also npx -y @justfortytwo/guide once published.
As a library
import { openDb, runMigrations, OllamaEmbedder, store, recall } from '@justfortytwo/guide';
const h = openDb('memory.db');
await runMigrations(h.k);
const embedder = new OllamaEmbedder();
await store(h, embedder, { content: 'the deploy script lives in scripts/deploy.sh', source: 'owner', observed: 'stated' });
const hits = await recall(h, embedder, 'how do I deploy?', 5);
As a Claude Code plugin
.claude-plugin/plugin.json declares the plugin; .mcp.json registers the
fortytwo-guide server. By default it launches via npx:
{
"mcpServers": {
"fortytwo-guide": {
"command": "npx",
"args": ["-y", "@justfortytwo/guide"],
"env": {
"OLLAMA_BASE_URL": "http://localhost:11434",
"EMBED_MODEL": "qwen3-embedding:0.6b",
"DB_PATH": "${CLAUDE_PLUGIN_DATA}/memory.db"
}
}
}
}
${CLAUDE_PLUGIN_DATA} survives plugin updates, so the DB persists across
upgrades. When developing from source, build first (npm run build) and swap
the command to node with args ["${CLAUDE_PLUGIN_ROOT}/dist/index.js"].
Claude Code does not build MCP servers — they run via npm/npx.
Continuous enrichment
enrich(h, embedder, candidates) folds a batch of candidate memories into the
store: it drops low-salience candidates, dedupes near-duplicates by meaning,
and writes the survivors with provenance — honoring an explicit supersedes to
replace a stale belief (history is kept, never a silent overwrite).
enrichFromTurn(h, embedder, turn, extractor) runs an injected SalienceExtractor
and feeds its candidates to enrich.
The salience extractor itself is model-driven and lives in the sibling
@justfortytwo/deepthought engine (a SalienceExtractor with an injected
LlmClient) — guide owns only the dedupe + write, never the model call.
Peer seams
guide depends on two sibling packages one-directionally (declared as optional peers, no cycle):
@justfortytwo/vogon— guide shipsVogonApprovalStore(src/vogon-approval-store.ts), a durable SQLite-backed implementation of vogon'sApprovalStore+AuditLoggerinterfaces. Pass it to vogon'sdecide(..., { store, audit })to back the safety gate's one-shot approvals with guide's db instead of the gate's standalone JSONL store.@justfortytwo/deepthought— the model-driven salience extractor injected intoenrichFromTurn(see above).
Development
npm run build # tsc
npm test # vitest run
npm run test:watch # vitest
Set RUN_OLLAMA_TESTS=1 to run the opt-in live-Ollama embedder test.
License
MIT © 2026 Enrico Deleo
Created and maintained by Enrico Deleo.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.