decisionnode/DecisionNode
Record development decisions as structured JSON, embed them as vectors via Gemini, and search semantically over MCP. Works with Claude Code, Cursor, Windsurf, and any MCP client.
README
<p align="center"> <img src="website/src/assets/images/DecisionNode-transparent.png" width="150" /> </p>
<h1 align="center">DecisionNode</h1>
<p align="center"> Record a decision, embed it as a vector, search it later.<br/> One store shared across all your AI tools: Claude Code, Cursor, Windsurf, and any MCP client. </p>
<p align="center"> <img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT" /> <img src="https://img.shields.io/npm/v/decisionnode.svg" alt="npm version" /> <img src="https://github.com/decisionnode/DecisionNode/actions/workflows/ci.yml/badge.svg" alt="CI" /> <a href="https://glama.ai/mcp/servers/decisionnode/DecisionNode"><img src="https://glama.ai/mcp/servers/decisionnode/DecisionNode/badges/score.svg" alt="Glama" /></a> </p>
<p align="center"> <img src="website/public/recordings/demo.gif" alt="DecisionNode Demo" width="800" /> </p>
Record a decision, embed it as a vector, search it later. One store shared across all your AI tools: Claude Code, Cursor, Windsurf, and any MCP client.
Not a markdown file — structured decisions with semantic search, exposed over MCP.
Install
npm install -g decisionnode
cd your-project
decide init # creates project store
decide setup # configure Gemini API key (free tier)
# Connect to Claude Code (run once)
claude mcp add decisionnode -s user decide-mcp
How it works
- A decision is made — via
decide addor the AI callsadd_decisionthrough MCP - Embedded as a vector — using Gemini's
gemini-embedding-001, stored locally invectors.json - AI retrieves it later — calls
search_decisionsvia MCP, gets back relevant decisions ranked by cosine similarity
The retrieval is explicit — the AI calls the MCP tool to search. Decisions are not injected into a system prompt.
Two interfaces
CLI (decide) |
MCP Server (decide-mcp) |
|
|---|---|---|
| For | You | Your AI |
| How | Terminal commands | Structured JSON over MCP |
| Does | Setup, add, search, edit, deprecate, export, import, config | Search, add, update, delete, list, history |
Both read and write to the same local store (~/.decisionnode/).
Quick reference
decide add # interactive add
decide add -s UI -d "Use Tailwind" # one-command add
decide add --global # applies to all projects
decide search "error handling" # semantic search
decide list # list all (includes global)
decide deprecate ui-003 # soft-delete (reversible)
decide activate ui-003 # bring it back
decide check # embedding health
decide embed # fix missing embeddings
decide export json > decisions.json # export to file
Features
<details> <summary><strong>History tracking</strong> — full audit trail with source tracking</summary> <br/> Every add, edit, deprecation, and delete is logged. The history shows which tool made each change — <code>cli</code> for terminal commands, or the MCP client name (<code>claude-code</code>, <code>cursor</code>, <code>windsurf</code>) for AI-initiated changes.
<img src="website/public/recordings/history.gif" alt="decide history" width="700" /> </details>
<details> <summary><strong>Conflict detection</strong> — catch duplicates before they're saved</summary> <br/> When adding a decision, existing decisions are checked at 75% similarity. The CLI warns you and asks to confirm. The MCP server returns the conflicts so the AI can decide whether to update, deprecate, or force-add.
<img src="website/public/recordings/conflict.gif" alt="conflict detection" width="700" /> </details>
<details> <summary><strong>Deprecate / Activate</strong> — soft-delete without losing embeddings</summary> <br/> Deprecated decisions are hidden from search but their embeddings are preserved. Reactivate them later and they're immediately searchable again — no re-embedding needed.
<img src="website/public/recordings/deprecate.gif" alt="deprecate and activate" width="700" /> </details>
<details> <summary><strong>Global decisions</strong> — shared across all projects</summary> <br/> Decisions like "never commit .env files" or "always use TypeScript strict mode" can be marked as global. They're stored separately and automatically included in every project's search results.
<img src="website/public/recordings/global.gif" alt="global decisions in search" width="700" /> </details>
<details> <summary><strong>Agent behavior</strong> — control how aggressively the AI searches</summary> <br/> This setting changes the <code>search_decisions</code> tool description sent to the AI. <strong>Strict</strong> (default) tells the AI searching is mandatory before any code change. <strong>Relaxed</strong> lets the AI decide when searching is relevant.
<img src="website/public/recordings/behavior.gif" alt="agent behavior strict vs relaxed" width="700" /> </details>
<details> <summary><strong>Configurable threshold</strong> — filter out weak matches</summary> <br/> Set the minimum similarity score (0.0–1.0) for search results. The default is 0.3. Raise it to reduce noise, lower it to surface more loosely related decisions. Applies to both CLI and MCP searches.
<img src="website/public/recordings/threshold.gif" alt="configurable search threshold" width="700" /> </details>
<details> <summary><strong>Embedding health</strong> — check and fix missing vectors</summary> <br/> <code>decide check</code> shows which decisions are missing embeddings. <code>decide embed</code> generates them. <code>decide clean</code> removes orphaned vectors from deleted decisions.
<img src="website/public/recordings/embed.gif" alt="decide check and decide embed" width="700" /> </details>
Documentation
Full docs at decisionnode.dev/docs
- Quickstart
- CLI Reference — all commands
- MCP Server — 9 tools, setup for Claude/Cursor/Windsurf
- Decision Nodes — structure, fields, lifecycle
- Context Engine — embedding, search, conflict detection
- Configuration — storage, agent behavior, search threshold, global decisions
- Workflows — common patterns
For LLM consumption: decisionnode.dev/decisionnode-docs.md
Contributing
See ROADMAP.md for what's coming next. Bug fixes, features, docs improvements, or just ideas are all welcome. See CONTRIBUTING.md for how to get started.
License
MIT — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。