Skip to main content
Glama
ontorata

Ratary Memory

by ontorata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Ratary Memory

Related Servers

  • Kronvex

    Daftgoldens
    A
    license
    A
    quality
    D
    maintenance
    Persistent memory API for AI agents — store, recall, and inject semantically-searchable context across sessions. EU-hosted, GDPR-compliant. Supports Claude, Cursor, Cline, and any MCP-compatible client.
    4
    2
    MIT

  • ContextFS

    contextfs
    A
    license
    Not graded
    quality
    C
    maintenance
    Universal AI memory layer that provides cross-client, cross-repo context management with semantic search, automatic code indexing, and session management. Enables persistent developer memory across projects with typed memories, graph-based relationships, and RAG-powered retrieval.
    5
    MIT

  • universal-memory

    YanAmorelli
    A
    license
    C
    quality
    A
    maintenance
    A vendor-agnostic cognitive persistence layer for AI agents. Eliminate the "repetition tax" by transporting your context, preferences, and history across sessions. Features an auto-adaptation engine that syncs global instructions to ensure operational cohesion and optimize token usage across any LLM or multi-agent workflow.
    38
    6
    Apache 2.0

  • Sovereign Universal Memory MCP

    nnaveenraju
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides a persistent, vendor-neutral memory layer that allows AI tools and agents to share context and knowledge across different platforms while maintaining local data ownership. It enables users to store, recall, and manage structured memories through hybrid semantic search and automated context assembly.
    3 npm
    Apache 2.0

  • Cortex Hub

    lktiep
    A
    license
    Not graded
    quality
    A
    maintenance
    Self-hosted AI Agent Memory + Code Intelligence Platform providing persistent memory, AST-aware code search, and quality enforcement via a single MCP endpoint.
    58
    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.6/5.0

Scored across 6 tools

Disambiguation5/5

Each tool serves a distinct purpose: capabilities discovery, context assembly, single memory fetch, client listing, memory creation, and memory search. No two tools overlap in functionality, and descriptions clearly differentiate them.

Naming Consistency5/5

All tool names follow the consistent verb_noun pattern with underscores: get_capabilities, get_context, get_memory, list_agent_clients, save_memory, search_memory. No mixing of conventions.

Tool Count5/5

With 6 tools, the set is well-scoped for a memory management server. Each tool addresses a fundamental operation, and the count is neither too sparse nor excessive for the domain.

Completeness3/5

The tools cover creation (save_memory) and read operations (get_memory, search_memory, get_context), but lack update and delete tools. This leaves a notable gap in memory lifecycle management, though the core retrieval and storage are handled.

Maintenance

ActivitySlowing
ResponsivenessUnresponsive

Resources