MCP Servers · Memory
decisionnode/DecisionNode
CLI + Local MCP - A shared structured memory store across Claude Code, Cursor, Windsurf, Antigravity, and every MCP client. Semantically queryable.
Our verdict
We have not reviewed decisionnode/DecisionNode yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About decisionnode/DecisionNode
DecisionNode is a CLI tool that provides a local, shared structured memory store for MCP-based coding assistants. It works with Claude Code, Cursor, Windsurf, Antigravity, and any MCP client. The store is semantically queryable.
Best for
Developers who want a consistent memory layer across multiple MCP-based coding assistants
Use cases
- Share structured memory across multiple AI coding assistants
- Query stored knowledge semantically from any connected tool
- Build a persistent context layer for AI-assisted development
Notes
39 stars on GitHub. Last updated 2026-04-15. Licensed MIT.
Pros
- Works with multiple AI coding assistants without per-tool setup
- Data stays local and under your control
- Simple CLI interface for managing structured memory
Cons
- Low community adoption and limited documentation
- Dependency on MCP protocol, only works with compatible clients
- Requires command line comfort for setup and use
Key facts
What we have checked
Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Install
npm install -g decisionnodeTools exposed
add_decisionsearch_decisionsupdate_decisiondelete_decisionlist_decisionsget_decision_historydeprecate_decisionactivate_decisionget_decision
Clients the listing names (not checked here)
Claude Code, Cursor, Windsurf, Antigravity
Install
Add decisionnode/DecisionNode to your client
No install recipe yet. We write one for Claude Code, Claude Desktop, Cursor, VS Code, Codex and ChatGPT when the server is in the official MCP registry with a package or remote address we can use.
Until then, follow the project's own README, or the setup the listing publishes under How to set it up.
Works with
What decisionnode/DecisionNode connects to
No confirmed connections yet. A product appears here when the server's registry name, repo, homepage or name ties it to that product, and a client appears when we have an install recipe for it.
Alternatives
Alternatives to decisionnode/DecisionNode
| Record | Type | How we know | Checked |
|---|---|---|---|
| topoteretes/cogneeThis is an alternative to it | MCP server | Named in the listing | Not dated |
| vectorize-io/hindsightThis is an alternative to it | MCP server | Named in the listing | Not dated |
Compare
Compare decisionnode/DecisionNode side by side
Sources
Where this comes from
No sources recorded yet. Each source we check is listed here with the date we checked it.
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Open-source & AI alternatives
Swap-in tools that solve the same job. Weigh the trade-offs before you commit.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.