Skip to main content
Glama
WebRTCGame

SQLite Project Memory MCP

by WebRTCGame

Related Servers

Alternatives to SQLite Project Memory MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      A knowledge graph memory server using SQLite to provide persistent, isolated contexts for organizing information into searchable categories like work and personal projects. It features unique ID-based operations and a token-efficient serialization format designed to optimize interactions with LLMs.
      11
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A persistent AI memory server that enables storage and retrieval of context and project artifacts across conversations. It features full-text search, version history, and automatic content chunking using local SQLite or hosted cloud storage.
      2 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A database-backed MCP server that acts as a project memory bank, enabling AI assistants to store, retrieve, and search structured context like decisions, tasks, and architecture using SQLite and vector embeddings.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A persistent memory server for AI agents that stores structured notes in a local SQLite database with full-text search and graph-based relationships. It features 32 specialized tools for managing long-term context, including version history, automated TTL expiration, and complex filtering.
      20 npm
      MIT

    TDQS

    C2.8/5.0

    Scored across 41 tools

    Disambiguation3/5

    The tools cover distinct operations like entity management, graph relationships, content handling, and queries, but there is notable overlap in some areas. For example, create_entity, get_or_create_entity, and upsert_entity have overlapping purposes for entity creation, and append_content vs. write_content could cause confusion in content addition. Descriptions help clarify, but agents might misselect between these similar tools.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun or verb_adjective_noun pattern (e.g., create_entity, list_entities, get_entity_graph), with clear and descriptive names. There are minor deviations like server_info (noun_verb) and apply_performance_tuning (verb_noun_noun), but overall the naming is predictable and readable across the set.

    Tool Count2/5

    With 41 tools, the count is excessive for a project memory server, leading to potential cognitive overload and inefficiency. While the domain is broad, many tools could be consolidated or streamlined (e.g., multiple entity creation tools, overlapping content tools), making it feel heavy and less well-scoped than ideal for agent use.

    Completeness5/5

    The tool set provides comprehensive coverage for project memory management, including full CRUD operations for entities and relationships, content handling, graph traversal, queries, snapshots, health checks, and context management. There are no obvious gaps; agents can perform all core workflows from initialization to archiving and reporting without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues