Skip to main content
Glama
decisionnode

decisionnode/DecisionNode

Official
by decisionnode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to decisionnode/DecisionNode

  • Tribal by tribal-memory

    Tribalofficial

    tribal-memory
    F
    license
    A
    quality
    A
    maintenance
    Semantic memory for AI builders: capture the tacit engineering know-how that never reaches your docs, recall it the moment it applies. Built in Rust on Postgres and pgvector.
    10
    10
    -

Related Servers

  • Kage

    kage-core
    A
    license
    A
    quality
    A
    maintenance
    Shared, code-grounded memory for developers and their coding agents. Capture a learning once and the whole team plus every agent recalls it; memory is grounded in your code and stored as git-tracked JSON reviewed in PRs, with citations validated on write and stale memory withheld from recall. Works with any MCP client.
    11
    33
    GPL 3.0

  • cogmemai-mcp

    hifriendbot
    A
    license
    A
    quality
    C
    maintenance
    Persistent cloud memory for AI coding assistants. 28 MCP tools for semantic search, auto-learning, task tracking, correction patterns, knowledge graphs, and session replay across Claude Code, Cursor, Windsurf, Cline, and any MCP client. Encrypted at rest. Team shared memory with author attribution.
    35
    223 npm
    7
    MIT

  • porque

    MiguelOvejeroD
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables capturing and storing AI coding decisions as markdown, and provides MCP tools for assistants to query and record those decisions so they respect past architectural choices.
    MIT
  • Trapic Core by trapicAi

    Trapic Coreofficial

    trapicAi
    A
    license
    Not graded
    quality
    D
    maintenance
    Self-hosted MCP server for long-term memory in AI coding assistants, capturing decisions, conventions, and discoveries as structured traces with tag and keyword search.
    2
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 9 tools

Disambiguation5/5

Each tool serves a distinct purpose: add/delete/get/update for individual decisions, list/search for retrieval, history for changelog, status for overview, and list_projects for context. No overlapping functionality.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case, e.g., add_decision, search_decisions, list_projects. No mixing of styles or ambiguous verbs.

Tool Count5/5

9 tools cover the decision management domain without excess or deficiency. Each tool earns its place, supporting CRUD, search, history, status, and project context.

Completeness5/5

The tool surface covers full lifecycle: creation, retrieval, update, deletion, listing, searching, history tracking, and status overview. No obvious gaps for typical decision management workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources