Skip to main content
Glama
mcasdfgf

MCP Roo Memory

by mcasdfgf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Roo Memory

No user-submitted related servers found.

    Related Servers

    • M.I.M.I.R - Multi-agent

      orneryd
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI assistants with persistent graph database memory using Neo4j, enabling task management, relationship understanding, semantic search with embeddings, file indexing, and multi-agent coordination through the Model Context Protocol.
      18 npm
      285
      MIT

    • codebase-memory

      yuga-hashimoto
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent memory for AI coding agents through the Model Context Protocol, enabling them to store and retrieve project knowledge across sessions.
      26 npm
      MIT

    • Memora

      VnemAIDev
      A
      license
      Not graded
      quality
      C
      maintenance
      A local, persistent, semantically-aware knowledge graph for AI coding agents like Claude Code, providing efficient session memory with minimal token cost and zero runtime network calls.
      MIT

    This server cannot be deployed

    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

    A3.9/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose. Desktop tools manage sessions and viewports, graph tools handle node and relation CRUD plus traversal, and vector tools handle semantic search and storage. Even similar-sounding tools like graph_search and vector_search are well-differentiated by their mechanics.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern, predominantly verb_noun (e.g., graph_add_node, vector_search). The naming is predictable and makes the tool's action and target clear.

    Tool Count4/5

    17 tools is slightly above the ideal 3-15 range, but the set is well-scoped for a memory server covering graph operations, search, session management, and temporal navigation. Each tool serves a distinct need without being excessive.

    Completeness4/5

    The tool surface covers CRUD for nodes, relations, search, session initialization, and temporal queries. Minor gaps exist (e.g., no direct relation deletion tool), but core workflows are fully supported with workarounds available.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources