Skip to main content
Glama
Ratary Memory

Ratary Memory

by ontorata

Related Servers

Alternatives to Ratary Memory

Related Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Serves AI agents a shared persistent memory that ingests Obsidian vaults, code, transcripts, bookmarks, and session or bug-fix captures, then classifies, promotes, and synthesizes them into tiered, retrievable knowledge. Exposes token-optimized context briefings and hybrid keyword/semantic search over MCP so multiple agents can read and write the same brain and improve across sessions.
    5 npm
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Gives AI agents persistent, shared memory by ingesting notes, code, transcripts, and session captures, then serving token-optimized context and hybrid keyword/semantic search over MCP and REST. Agents can classify, promote, and synthesize stored material so each session builds on prior work instead of starting from zero.
    5 npm
    MIT
  • 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
  • A
    license
    Not graded
    quality
    A
    maintenance
    Gives every AI agent a shared, persistent memory by ingesting Obsidian vaults, code, transcripts, bookmarks and terminal sessions into a three-tier SQLite FTS5 store, then serving token-optimized hybrid retrieval, classification, promotion and cross-source synthesis over MCP and REST. This lets multiple agents read from and write to one compounding brain so each session starts with better context than the last.
    5 npm
    MIT
  • 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.
    6
    MIT

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

ActivityInactive
ResponsivenessUnresponsive