Skip to main content
Glama
stevepridemore

Graph-Memory

by stevepridemore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Graph-Memory

  • Amber by ambermem

    Amberofficial

    ambermem
    A
    license
    A
    quality
    B
    maintenance
    Gives your AI persistent memory across conversations. Stores facts automatically, finds them by meaning using hybrid search with query expansion, and organizes everything into topics without manual tagging.
    18
    1
    MIT

Related Servers

  • Memora

    VnemAIDev
    A
    license
    Not graded
    quality
    C
    maintenance
    A local, persistent, semantically-aware knowledge graph for AI coding agents like Claude Code, providing efficient session memory with minimal token cost and zero runtime network calls.
    MIT

  • Claude Code Memory Server

    ViralV00d00
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides persistent memory capabilities for Claude Code using Neo4j graph database to track development tasks, code patterns, solutions, and their relationships across sessions and projects, enabling contextual assistance and pattern recognition.
    11
    -

  • Synapse

    alexsh88
    F
    license
    Not graded
    quality
    A
    maintenance
    A self-hosted, temporal knowledge-graph memory for AI coding agents — shared across projects, queryable across time, written and read via MCP by any Claude Code session.
    -

  • chatgpt-kg

    Aaditya-git
    F
    license
    Not graded
    quality
    D
    maintenance
    Builds a personal knowledge graph from selected ChatGPT conversations (stored in Neo4j) and exposes it to Claude Code as an on-demand MCP search tool.
    -
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.5/5.0

Scored across 23 tools

Disambiguation5/5

Every tool has a clearly distinct purpose: audit, boost, build context, find communities, contradictions, run cypher, decay, delete, browse entities, export, ingest, merge, suggest merges, prune, query, read transcript, re-embed, relate, search, stats, unmerge, validate, weaken. No two tools overlap in function.

Naming Consistency5/5

All tool names follow the consistent pattern 'graph_' + lowercase_snake_case action verb or noun (e.g., graph_audit, graph_boost, graph_build_context). No mixing of camelCase or other conventions, making prediction easy.

Tool Count4/5

With 23 tools, the server covers the full lifecycle of a knowledge graph (CRUD, maintenance, quality, analysis). While on the high side, each tool is justified; it could be trimmed slightly but is not excessive.

Completeness5/5

The tool set provides comprehensive coverage: entity creation via graph_relate, reading via multiple tools, updating via boost/weaken/merge/reembed, deletion via delete/prune, plus management (export, ingest, decay, validate, contradictions, merge suggestions, unmerge, audit, build context, communities, stats, read transcript, cypher). No obvious gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources