Skip to main content
Glama
darknodebros

EleSync

by darknodebros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to EleSync

  • agent-memory-os

    yamantaka520
    A
    license
    A
    quality
    A
    maintenance
    Local-first memory engine for AI-agent teams: private/team/project ACL, associative recall, and federated sync across nodes. One SQLite file, no LLM required.
    12
    5
    Apache 2.0

Related Servers

  • auxly-memory-cli

    Tzamun-Arabia-IT-Co
    A
    license
    Not graded
    quality
    A
    maintenance
    Local-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.
    2
    MIT

  • memroam

    apurv101
    A
    license
    Not graded
    quality
    B
    maintenance
    Portable AI memory that roams with you across models and harnesses — one shared memory for Claude Code, Codex, Cursor, Gemini CLI and more, stored as plain markdown files you own. Per-project spaces plus a shared layer, vault-wide search; runs locally over stdio/HTTP or hosted with OAuth 2.1 backed by your own GitHub repo.
    43 npm
    MIT
  • afair by afairai

    afairofficial

    afairai
    A
    license
    A
    quality
    A
    maintenance
    The open-source, self-organizing memory for all your AI tools. Persistent memory over MCP (remember, recall, observe): background agents extract entities, resolve conflicts, and keep cited syntheses current in an append-only, encrypted, single-tenant vault.
    3
    6
    AGPL 3.0

  • 1AIVault

    stoicsoft
    F
    license
    Not graded
    quality
    D
    maintenance
    Portable AI memory vault — save memories, skills, and configs to a local database and share them across Claude Desktop, Claude Code, Cursor, Cline, and more.
    1
    -

  • NeuroStack

    raphasouthall
    A
    license
    Not graded
    quality
    A
    maintenance
    A local-first CLI and MCP server that helps you build and search a personal knowledge vault from Markdown notes, with semantic search and AI-powered features like stale note detection and session memory harvesting. It’s provider-agnostic, requires no GPU in its default mode, and exposes your vault as long-term memory to any MCP-compatible AI tool like Claude Code.
    47
    Apache 2.0

  • wadachi

    EliaCinti
    A
    license
    B
    quality
    B
    maintenance
    Persistent memory for AI agents built on the LLM Wiki pattern: a plain-Markdown brain (also a valid Obsidian vault) with SQLite metadata, local semantic search via fastembed (no API keys), one-call session context with project auto-detection, and a decision log with rationale. Works with Claude Code, Claude Desktop, Cursor, and any MCP client.
    31
    MIT
Deploy Server
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

TDQS

A3.6/5.0

Scored across 12 tools

Disambiguation5/5

Each tool has a distinct purpose: project_context vs recall_project, remember vs save_project_document, and memory-specific tools (forget, history, find_conflicts) are clearly separated. No overlaps that could confuse an agent.

Naming Consistency2/5

Naming is inconsistent: some tools use verb-first patterns (recall, list, save, remember, forget), while others are noun-first or standalone nouns (project_context, memory_status, history, audit_log). The mix of underscore and single-word forms (e.g., list_scopes vs recall_project) further reduces predictability.

Tool Count4/5

12 tools is a reasonable number for a server that combines memory management and project context. It covers the core operations without being overwhelming, though a few could potentially be merged.

Completeness3/5

Memory operations are well covered (create, read, update via supersedes, delete, search, status, audit). However, project tools lack update/delete capabilities for projects and documents, leaving a notable gap in lifecycle management.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources