Skip to main content
Glama
Sign In
easy-agent-mem

easy-agent-mem

by atharvavdeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to easy-agent-mem

Related Servers

  • kmp-mcp

    underpass-ai
    A
    license
    Not graded
    quality
    A
    maintenance
    Provides a local stdio MCP server that gives AI coding agents a typed, temporal, evidence-backed memory on embedded SQLite, letting them record decisions and constraints, ask why something happened, navigate memory by time, trace proof paths between refs, and export or supersede stored state without rewriting it. It also exposes read-only ChronoLoom view tools so a person and their agent can steer the same multidimensional memory view by semantic intent rather than raw coordinates.
    Apache 2.0

  • memnant

    peureka
    A
    license
    Not graded
    quality
    A
    maintenance
    Persistent memory MCP server that remembers decisions and context across coding sessions, automatically logging and surfacing relevant knowledge as you work.
    116 npm
    MIT

  • coster

    savai15
    A
    license
    Not graded
    quality
    A
    maintenance
    MCP server that provides offline-first, persistent memory for AI coding assistants. It captures project decisions and conventions into a local SQLite database and syncs them to tool-specific memory files like CLAUDE.md and AGENTS.md.
    15 npm
    MIT

  • SuperBased Observer

    superbasedapp
    F
    license
    Not graded
    quality
    A
    maintenance
    Local MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.
    51
    -
  • AI Dimag

    AI Dimagofficial

    AiDimag
    A
    license
    A
    quality
    A
    maintenance
    MCP server that gives coding agents persistent, verified memory of codebase decisions, conventions, and skills, with evidence-based claims that are re-checked via git hooks and human-gated review. Enables memory search, propose/approve, chat harvesting, and critique across MCP-compatible tools.
    21
    112 npm
    1
    MIT
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

B3/5.0

Scored across 11 tools

Disambiguation4/5

Most tools have clearly distinct scopes: retrieval (query_memory, get_task_context, get_review_memory, get_session_handoff), writing (record_decision, record_review_outcome, summarize_to_obsidian), and session inspection (session_status, list_recent_sessions). There is some adjacency among the three retrieval tools and between session_status and get_session_handoff, but the descriptions give enough signals (citations/budget vs. raw memory vs. review findings vs. session handle) to pick correctly.

Naming Consistency4/5

Predominantly consistent verb_noun snake_case (record_decision, query_memory, get_review_memory, check_decisions, list_recent_sessions). Minor deviations exist: session_status is a bare noun phrase with no verb, and summarize_to_obsidian adds a preposition plus a backend-specific name, which is less predictable than the rest.

Tool Count5/5

Eleven tools is well within a healthy range and each maps to a concrete memory-lifecycle action (record, query, verify, share, summarize, handoff, inspect session). No redundant near-duplicates bloat the surface.

Completeness3/5

Core read/write paths for decisions, review evidence, sharing, summaries, and session handoff are covered. However, there is no explicit delete/forget/prune or supersede operation for a memory system where stale or private data must be removed, and check_decisions flags problems without any tool to resolve them, leaving dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources