What is the key difference between DecisionNode and Memora?

DecisionNode belongs to the Knowledge & Memory category with local stdio execution, while Memora belongs to the Knowledge & Memory category with local stdio execution.

How do I install DecisionNode or Memora in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are DecisionNode and Memora free or paid?

DecisionNode operates under a Free / Open Source model (No auth required). Memora operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

DecisionNode lists 6 tools with 1 views and 83 GitHub stars. Memora lists 6 tools with 2 views and 719 GitHub stars.

Can I use both DecisionNode and Memora together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

DecisionNode vs Memora

In-depth architectural comparison of the DecisionNode and Memora MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

DecisionNode

Knowledge & Memory · Local stdio

Quality: 44/100 (Fair) | Auth: No auth required

Memora

Knowledge & Memory · Local stdio

Quality: 56/100 (Good) | Auth: API Key required

Verdict Summary: Choose DecisionNode if you need specialized Knowledge & Memory tools running via a local process. Choose Memora if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose DecisionNode when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Store decisions as JSON with fields like id, scope, status, rationale, and constraints, Embed decisions using Gemini embedding model for semantic search, CLI commands for adding, searching, editing, deprecating, and exporting decisions.

Explore DecisionNode Details

Choose Memora when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: MEMORA_DB_PATH, MEMORA_STORAGE_URI, CLOUDFLARE_API_TOKEN, AWS_PROFILE, AWS_ENDPOINT_URL, MEMORA_CLOUD_ENCRYPT, MEMORA_ALLOW_ANY_TAG, MEMORA_GRAPH_PORT.

Feature & Specification Comparison

Specification	DecisionNode decisionnode Knowledge & Memory	Memora agentic-mcp-tools Knowledge & Memory
Summary	Record development decisions as structured JSON, embed as vectors via Gemini, and search semantically over MCP. Shared store across Claude Code, Cursor, Windsurf, and any MCP client. CLI + MCP server, local-only, free Gemini embedding tier.	Persistent memory with knowledge graph visualization, semantic/hybrid search, cloud sync (S3/R2), and cross-session context management.
Category & Scope

Tools & Capabilities Breakdown

DecisionNode Tools (6)

Store decisions as JSON with fields like id, scope, status, rationale, and constraints

Embed decisions using Gemini embedding model for semantic search

CLI commands for adding, searching, editing, deprecating, and exporting decisions

MCP server interface exposing add, search, update, delete, list, and history actions

Local web UI showing graph, vector space, and list views of decisions

Conflict detection on similar decisions and full audit trail with source tracking

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

DecisionNode Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "decisionnode-decisionnode": {
      "command": "npx",
      "args": [
        "-y",
        "decisionnode-decisionnode"
      ]
    }
  }
}

Memora Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "agentic-mcp-tools-memora": {
      "command": "npx",
      "args": [
        "-y",
        "wrangler"
      ],
      "env": {
        "MEMORA_DB_PATH": "YOUR_MEMORA_DB_PATH_HERE",
        "MEMORA_STORAGE_URI": "YOUR_MEMORA_STORAGE_URI_HERE",
        "CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE",
        "AWS_PROFILE": "YOUR_AWS_PROFILE_HERE",
        "AWS_ENDPOINT_URL": "YOUR_AWS_ENDPOINT_URL_HERE",
        "MEMORA_CLOUD_ENCRYPT": "YOUR_MEMORA_CLOUD_ENCRYPT_HERE",
        "MEMORA_ALLOW_ANY_TAG": "YOUR_MEMORA_ALLOW_ANY_TAG_HERE",
        "MEMORA_GRAPH_PORT": "YOUR_MEMORA_GRAPH_PORT_HERE"
      }
    }
  }
}

Frequently Asked Questions

DecisionNode is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memora belongs to Knowledge & Memory using local stdio subprocess. Select DecisionNode when you need capabilities focused on knowledge & memory and Memora when you require tools for knowledge & memory.

More alternatives to DecisionNode More alternatives to Memora Knowledge & Memory category hub Canonical compare URL