Skip to main content
Glama
Sign In
amnesic

amnesic

by SurajKGoyal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to amnesic

No user-submitted related servers found.

    Related Servers

    • engram-mcp

      Cartisien
      A
      license
      A
      quality
      C
      maintenance
      Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings with keyword fallback. Tools: remember, recall, history, forget, stats.
      17
      37 npm
      1
      MIT

    • sqlite-local-ai-memory

      cheveguerra
      A
      license
      A
      quality
      B
      maintenance
      Simple, fast, long-term memory for your AI chatbots, agents, and MCP tools. Give your LLM a persistent memory using a local SQLite file. No complex database servers, no heavy cloud setup, and zero C++ compilation errors. Works everywhere.
      14
      5
      132 npm
      1
      MIT

    • claude-memory-mcp

      imshota1009
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent long-term memory for LLMs via local SQLite storage and semantic search, enabling recall across sessions without external APIs.
      15 npm
      5
      MIT

    • io.github.oxgeneral/agentmem

      oxgeneral
      A
      license
      Not graded
      quality
      D
      maintenance
      Lightweight persistent memory for AI agents using a single SQLite file with hybrid search (keywords + semantics). Zero to 12MB install, no cloud or server required.
      7
      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.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose. There is no overlap: annotation management (annotate, deprecate, forget), schema retrieval (get_schema, list_tables), querying (query), searching (search), relationship discovery (discover_relationships, get_relationships), drift detection (detect_drift), and knowledge sync (sync_knowledge) are all separate concerns.

    Naming Consistency5/5

    All tools follow the consistent pattern `db_<verb>_<noun>` using snake_case. The verbs are descriptive and indicate the action (e.g., annotate, query, list_tables). No mixing of conventions or vague names.

    Tool Count5/5

    With 12 tools, the server is well-scoped for a database knowledge management system. Each tool serves a necessary function in the lifecycle of schema understanding, annotation, querying, and maintenance. Not overloaded nor sparse.

    Completeness4/5

    The tool set covers the core workflow: connection listing, table discovery, schema retrieval, querying, annotation CRUD (annotate, deprecate, forget), relationship discovery, drift detection, and knowledge sync. Missing a direct tool to view all annotations in isolation, but schema retrieval and search provide access.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Resources