Alimenter votre agent
Installation de l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
Pas encore de version packagée dans le registre. Suivez le README du dépôt.
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LancerDe l'éditeur
🧠 Wordcell hands the next agent session what this one learned. Decisions, plans, and sources live as Markdown files beside your code. Tie a note to the paths it explains, and an agent about to change that code gets the note first. Search matches exact words or meaning, with an optional local model, and every index rebuilds from files you can read in any editor.
Wordcell keeps decisions, plans, and sources as Markdown beside your code, so coding agents can find them from the file they are about to change.
Ask your agent to set it up: https://wordcell.io
Wordcell is a Markdown knowledge base and local MCP memory server for coding agents such as Claude Code, Codex, and Cursor. It keeps decisions, plans, and sources as Markdown files beside your code, and agents find them by exact words, by meaning with an optional local model, or from the file they are about to change.
A new coding-agent session needs the reasons behind the code it is changing. Wordcell keeps the decision, its supporting sources, and the plan that puts it into practice in a connected set of Markdown files. Tie a note to a repository path, and the next agent can recover that context before it edits the file. When an assumption changes, update the decision and keep its earlier reasoning in Git.
Captured sources preserve what you read, maintained notes explain what you
currently understand, and plans record the work and its results. Named
relationships such as evidenced-by and supersedes make those connections
available to the embedded Oh graph engine, whose results point back to the
supporting files. Optional local semantic search helps when the words in a
question differ from the note; Git history connects the explanation to its
commits and accompanying code changes.
Use the CLI, local MCP server, or TypeScript SDK from your existing agent and editor. The public Agent Skill teaches agents to recover context, maintain plans, and leave reusable decisions for later sessions. Exact search, backlinks, and Git history need no account or model. Every index rebuilds from files you can read in Obsidian or any text editor. Wordcell is free and open source.
Web capture, optional hosted reranking, and your agent's provider reach other services; Privacy and boundaries says what each one sends.
wordcell percolate suggests missing links for you to review without
writing them into your notes.Plain Markdown may be enough for a small set of notes. QMD is a good fit for local document retrieval and also supplies Wordcell's optional semantic search. Wordcell adds a connected workflow for repository context, authored relationships, Git evidence, and selective publishing. Compare the tradeoffs.
Wordcell keeps the record in Markdown files you own, rebuilds every index from those files, and lets the next session start from the notes for the file it is changing: the design every Hraness project shares. The thread through hraness follows that design across the projects, and the ALGAL vision states the bet behind it.
Bun 1.3.14 or newer and Git are required. The CLI and TypeScript SDK run with Bun. Install the versioned GitHub archive:
bun add --global --ignore-scripts https://github.com/hraness/wordcell/releases/download/v0.27.2/hraness-wordcell-0.27.2.tgz
wordcell --help
Prefer npm? The same release is mirrored there:
npm install --global --ignore-scripts @hraness/[email protected]
wordcell --help
Keep Bun in PATH for either installation. If your shell cannot find wordcell,
add your package manager's global executable directory to PATH and reopen the
terminal. Optional semantic search, browser capture, and PDF tools have
additional prerequisites.
Global Bun and npm installations on macOS and Linux check for updates daily
before a command starts. Updates require the GitHub CLI (gh) to verify the
release and preserve --ignore-scripts. An active command, MCP server, or
preview server prevents replacement until it exits. Both installed commands
share the same settings:
wordcell update status
wordcell update check
wordcell update
wordcell update disable
wordcell update enable
Use HRANESS_NO_UPDATE=1 wordcell … for an invocation without automatic update
requests, including offline work. Help, version output, and SDK imports never
check for updates. Source, project, copied, and Windows installations use manual
upgrades. Exact Bun registry versions stay pinned until update enable; npm
does not reliably retain the original global version constraint, so use
update disable when you need a fixed global version. A versioned GitHub archive
tracks verified releases by default. See the update reference.
Run this from a directory where you want a new kb/ folder. It creates one
Markdown note and finds it without a search model or hosted search service:
wordcell init kb
wordcell note create notes/parser-contract \
--title "Parser contract" --type concept --tag architecture \
--body "Parser retries stop after three attempts." --root kb
wordcell search "parser retries" --root kb --mode exact
The result includes notes/parser-contract and the saved retry constraint.
Open kb/notes/parser-contract.md to see the ordinary Markdown file. Wordcell
adds a stable document_id in its frontmatter; you can edit the prose normally.
Already have Markdown or an Obsidian vault? In v0.22.0 or newer, search
the existing folder without initialization or an index.md file:
wordcell search "a phrase from your notes" --root /path/to/your/vault --mode exact
Replace the path and phrase with your own. You don't need to initialize, convert, or move the existing files to search them.
After trying the CLI, install the public Agent Skill into a compatible agent, such as Claude Code, Codex, Cursor, or GitHub Copilot:
bunx skills add hraness/wordcell#v0.27.2 --skill wordcell
Then ask:
Use Wordcell to search for "parser retries" in ./kb using exact mode.
Read the matching note and explain the saved constraint.
The skill installs instructions, not a service. Installation does not create a vault, modify your notes, or grant an agent permission to access other accounts. The agent still follows its own provider and data-handling settings. Inspect the skill.
Link a plan to the decision you saved:
wordcell note create plans/parser-v2 \
--title "Parser v2" --type plan \
--body "The plan implements [[notes/parser-contract|the parser contract]]." \
--root kb
wordcell backlinks notes/parser-contract --root kb
The backlink result includes plans/parser-v2, so a later session can find the
work that depends on the constraint.
For code-path lookup, add this field inside the existing frontmatter of
kb/notes/parser-contract.md:
repository_scopes:
- packages/parser
From your repository root, use an actual path under that scope and inspect the
returned notes and inherited AGENTS.md guides:
wordcell context packages/parser/src/index.ts --root kb --repo .
Commit the vault with your repository to preserve its history, then use
wordcell history notes/parser-contract --root kb --repo . to inspect the
commits behind the note. History is optional and requires recorded Git commits.
These views recover saved decisions, related work, rules, and provenance. They do not reconstruct private chat or prove that the note is still correct. Open the returned Markdown and guides before acting on them.
Cloudflare Clef support is in the current source tree. The versioned release listed above does not include it. From a source checkout, run:
bun ./src/cli.ts search "why releases use immutable archives" --root kb --mode exact \
--rerank clef --rerank-limit 25 --limit 5 --json
This optional hosted reranker uses Cloudflare Clef (clef by default, or
--rerank-model clef-flash). It sends the query and candidate note identifiers,
titles, paths, and snippets to Cloudflare, needs CLOUDFLARE_ACCOUNT_ID and
CLOUDFLARE_API_TOKEN, and incurs provider charges. Enable it only for vaults you
approve for external processing; credentials alone never enable it. Exact
identities remain first; a provider failure retains the baseline order with a diagnostic. See the
setup, SDK examples, measured results, and limits.
Use --json for structured output and wordcell --help for the complete command
surface. Full command reference.
Preview the decision and plan from the example before writing an output folder:
wordcell publish --root kb --out site \
--include notes/parser-contract --include plans/parser-v2 --dry-run --json
Review the selection, then build and preview it:
wordcell publish --root kb --out site \
--include notes/parser-contract --include plans/parser-v2
wordcell serve --root site --port 8080
Open http://127.0.0.1:8080. You get readable pages, linked notes, and search
that runs in the browser. Upload the site/ folder to your chosen static host
when you want to share it; publish itself never uploads anything.
For a repeatable slice, use path patterns or combine folders, tags, metadata, code scopes, and linked neighborhoods:
wordcell publish --root kb --out site-notes \
--include-glob 'notes/**/*.md' --exclude-glob '**/draft-*' --dry-run --json
Preview reports show up to 20 selected IDs by default, with a total count and
selection digest. They keep note bodies out of the agent's context. Use
--list-limit to adjust that preview without changing what gets published. publish: false excludes a note, but selected
prose and attachments still need review before sharing: selection is not secret
redaction. Selection recipes and hosting guide.
wordcell mcp --root kb serves a vault to a local MCP client, such as Claude
Code, Claude Desktop, Cursor, or Codex, over standard input and output. The
client can search, list, and read notes, follow links, create notes, update a
note body at a known revision, and add typed relations. --read-only removes
the write tools. Connect Wordcell to your coding agent
shows the setup for each host.
With the Agent Skill, ask your agent to save the session. It writes a dated session note, links it to the notes it changed, and keeps a profile note for you or your project. Wordcell extracts no facts and writes no note on its own. Session memory and profiles.
To move from Supermemory, wordcell import supermemory turns saved Supermemory
API responses into Markdown notes. The migration guide
covers export, import, and what does not transfer, and the
Supermemory comparison lists when to
choose Supermemory instead. Sync with Git
keeps one vault current on several machines.
In the September 19, 2026 SciFact study of scientific abstracts, hosted Jev reranking placed a relevant result first for 161 of 300 queries, versus 101 with Wordcell exact search alone. These historical measurements do not evaluate Cloudflare Clef or Clef Flash. Results and method.
The comparison guide covers Markdown alone, QMD, Basic Memory, Obsidian, static publishing tools, Supermemory, Mem0, and Zep using their own documentation. Choose the smallest workflow that meets your needs.
The benchmarks page shows the SciFact results and the published results of Oh, the embedded memory framework, each with its source data and method. On all 500 LongMemEval-S questions, Oh semantic retrieval scored 88.87% and BM25 86.13% with the same reader and budget; on the measure Oh named before the run, its interval does not rule out a tie. Oh's scores measure its own memory-retrieval path, not a Wordcell vault.
repository/
├── AGENTS.md # rules that govern edits
├── packages/parser/
│ └── AGENTS.md # rules scoped to this code
└── kb/
├── index.md # authored or managed front door
├── articles/ # captured sources and assets
├── notes/ # maintained explanations
└── plans/ # decisions and outcomes
Markdown, YAML frontmatter, explicit wikilinks, and Git hold the record. Open the same files in Obsidian, a text editor, or ordinary file-search tools. Application code does not need to import Wordcell or its vault.
Wordcell is the Markdown knowledge base. Oh is the embedded memory framework that backs its named graph queries and source proofs. Markdown and Git remain authoritative. Query the graph immediately without an Oh account, service, or persisted database:
wordcell graph query --program backlinks --note notes/parser-contract --root kb --json
The result traces each returned link to its source note and revision. Only an explicit
wordcell graph rebuild --root kb writes .wordcell/oh.sqlite, the file stays
ignored and rebuildable, and nothing flows from the projection back into notes.
Backlinks and typed relationships come from authored links. Percolation
suggests connections for review and does not add inferred edges to notes.
Wordcell search combines its own exact matching with optional QMD local search and optional hosted Cloudflare Clef reranking. Oh also offers memory retrieval for applications; its conversation-memory benchmark scores measure that separate path. They do not establish Wordcell's retrieval or answer quality. How the integration works.
Graph proofs explain a supported derivation from a specific source revision. They do not prove that a note is true or that a missing relationship cannot exist. Graph queries and proof limits.
Add the same immutable release to a Bun project:
bun add --exact --ignore-scripts https://github.com/hraness/wordcell/releases/download/v0.27.2/hraness-wordcell-0.27.2.tgz
The SDK provides read-only vault sessions, metadata queries, search, graph proofs, Git context, and composable workflows. A session owns one snapshot; reopen it after Markdown changes. SDK and workflow examples show the public imports and lifecycle.
Start with the task you want to complete. Browse all guides on the documentation index.
Existing kb/, index.md, kb:// identifiers, and Markdown formats remain
compatible. Vault format reference.
Installation and runtime contract.
The same skill is included at node_modules/@hraness/wordcell/skills/wordcell/.
Version 0.22 adds selective static publishing and local preview. Choose notes,
folders, path patterns, metadata, or linked neighborhoods, then inspect a
bounded selection report before building. Existing vaults need no migration.
The deprecated kb command was removed in 0.21.0; use wordcell.
All release notes and upgrade instructions.
Run bun run check for source, architecture, package installation, types, and
native-helper validation. The site has its own bun run check under site/.
See Contributing, Security, and the MIT License.
wordcell support shows optional development support for Wordcell. Features stay
free and no account is required. Accounts presents current terms; the person
confirms any payment in their browser. Wordcell has no product newsletter and
does not look up an email address for support.
After useful standalone work, agents can receive a discovery record on stderr.
Read wordcell support protocol --json for the shared closeout procedure.
Help, diagnostics, evaluation, SDK calls and nested commands stay quiet.
HRANESS_SUPPORT=off or HRANESS_SUPPORT_AUDIENCE=off suppresses incidental
invitations. Explicit human terminal rendering requires
HRANESS_SUPPORT_AUDIENCE=human; the default audience is an agent, including in
a pseudo-terminal.
wordcell support dismiss disables invitations across participating tools on
this machine. snooze pauses them for thirty days, enable restores them, and
status --json shows their separate local preferences. These commands do not
change a vault, sign up or pay. Acknowledged invitations share a seven-day
cooldown; discovery itself does not consume it.
Wordcell keeps decisions, plans, and sources as Markdown beside your code, so coding agents can find them from the file they are about to change.
Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
Wordcell s'exécute en local via stdio.
Dernière vérification : 2026-10-28. Wordcell keeps decisions, plans, and sources as Markdown beside your code, so coding agents can find them from the file they are about to change.