Skip to main content
Glama
Edlineas

AIVectorMemory

by Edlineas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AIVectorMemory

No user-submitted related servers found.

    Related Servers

    • Project Brain

      myczh-1
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP memory server that gives AI assistants durable project memory across coding sessions, storing context, changes, and decisions.
      3 npm
      1
      MIT

    • Mono Memory MCP

      potato-castle
      A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that provides AI assistants with a shared, persistent SQLite-backed memory for storing and retrieving project context, decisions, and discoveries. It enables cross-session continuity and team-wide knowledge sharing to keep AI coding tools aligned and informed.
      3
      MIT

    • myBrAIn

      lilium360
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides persistent memory and contextual awareness to language models, enabling project onboarding, recall of architectural rules, and code consistency across sessions.
      32
      MIT

    • Logica Context

      Rovemark
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides persistent, cross-session memory and team knowledge sharing for AI development workflows. It enables project DNA scanning, semantic search, context budgeting, and git-aware indexing to prevent AI context loss between sessions.
      65 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

    B3.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: memory storage/retrieval/deletion, code knowledge graph, README generation, session status, task management, and issue tracking. No two tools overlap significantly in functionality.

    Naming Consistency4/5

    All tool names use lowercase with underscores where needed, but they mix verb forms (forget, recall, remember) and noun forms (graph, readme, status, task, track). While consistent in style, the pattern is not strictly verb_noun, causing minor inconsistency.

    Tool Count5/5

    9 tools is well-scoped for a memory/vector database server that also handles code knowledge, tasks, issues, and session status. Each tool earns its place without redundancy.

    Completeness4/5

    The tool set covers core CRUD operations for memories, tasks, issues, and graph management. Minor gaps exist, such as lacking a bulk memory recall or listing all memories, but the overall surface is sufficient for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources