Enterprise DNA
M MCP Servers Developer low

decisionnode/DecisionNode

by Various

CLI + Local MCP - A shared structured memory store across Claude Code, Cursor, Windsurf, Antigravity, and every MCP client. Semantically queryable.

D

MCP

decisionnode/DecisionNode

Added 1 June 2026

#agentic-workflow #ai #anti-gravity #architectural-decisions #claude #claude-code #cli #cursor

Overview

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

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

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.

39 stars on GitHub. Last updated 2026-04-15. Licensed MIT.

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

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

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

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