Skip to main content
Glama
MikSkrzyp

identity-storage-mcp

by MikSkrzyp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to identity-storage-mcp

No user-submitted related servers found.

    Related Servers

    • engram

      tanvi-s18
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to store, recall, and manage persistent memory across sessions through MCP tools, with reviewable handoffs and SQLite-backed local storage.
      1
      MIT

    • misMEM

      lucasmella-stack
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent, cooperative memory for LLMs via MCP, with SQLite storage and tools for capturing, recalling, consolidating, crystallizing, and forgetting memories across sessions.
      3
      MIT

    • light-agent-memory-mcp-server

      AliYar-Khan
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.
      12
      5 npm
      MIT

    • nuzo-memory

      fabionfsc
      A
      license
      Not graded
      quality
      F
      maintenance
      Local-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.
      2
      Apache 2.0

    • recollect

      danbaileyza
      A
      license
      Not graded
      quality
      C
      maintenance
      Local, cross-agent memory for AI coding agents using a single SQLite file, enabling persistent sessions and durable facts shared across multiple MCP-compatible tools.
      8 npm
      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.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: memory_recall for browsing by tags/time, memory_search for content search, and memory_store for saving memories. No ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent 'memory_' prefix with a verb (recall, search, store), making the tool names predictable and easy to understand.

    Tool Count4/5

    With 3 tools, the set feels slightly minimal but appropriate for a targeted memory storage and retrieval system. The count is reasonable for the scope.

    Completeness3/5

    The tool surface covers storing and two retrieval methods, but lacks delete or update operations, which are notable gaps for a complete memory lifecycle.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources