Skip to main content
Glama
dennisdevulder

ltm

by dennisdevulder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to ltm

  • Longhand

    Wynelson94
    A
    license
    A
    quality
    A
    maintenance
    Persistent local memory for Claude Code that indexes every session's JSONL file verbatim into SQLite + ChromaDB. Exposes 17 MCP tools for semantic recall, deterministic file replay, and fuzzy "do you remember when..." queries across your entire session history — no API calls, nothing leaves the machine.
    17
    13
    MIT

  • agentmem

    Thezenmonster
    A
    license
    A
    quality
    D
    maintenance
    Governed memory for coding agents with trust lifecycle, conflict detection, staleness tracking, and health scoring. SQLite + FTS5, zero infrastructure. Works with Claude Code, Cursor, Codex, Windsurf.
    13
    3
    MIT

Related Servers

  • SloplessCode

    Utundry
    A
    license
    Not graded
    quality
    B
    maintenance
    Provides operational continuity for AI coding agents, preserving task state, decisions, checkpoints, and project context across sessions and model switches via MCP.
    1
    Apache 2.0

  • Mycelia

    kittors
    A
    license
    Not graded
    quality
    B
    maintenance
    Provides a persistent, cross-tool memory layer for AI coding agents via MCP, enabling storage and retrieval of decisions, preferences, and context across different tools and models.
    9
    1
    MIT

  • repomemory

    Lay4U
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server that captures and recalls coding session memory (failures, decisions, diffs) for AI agents, enabling cross-agent continuity and preventing repeated mistakes.
    48
    MIT
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored across 12 tools

Disambiguation5/5

Each tool has a clear, distinct purpose. For example, 'push' sends pre-built packets while 'save' persists session state, and 'show' returns a summary vs 'pull' returns raw JSON. No overlap causes confusion.

Naming Consistency4/5

All tool names are lowercase single words, but they mix short names (ls, rm) with full words (publish, resume) and a few noun forms (example, platform). While the style is uniform, the part-of-speech varies slightly.

Tool Count5/5

With 12 tools, the server covers core packet management (CRUD, listing, publishing, session saving) without being bloated. Each tool earns its place for a focused domain.

Completeness3/5

The tool set lacks an update operation for packet content (only delete+re-push). Additionally, there is no filtering or search capability beyond listing all packets. These are notable gaps for a complete lifecycle.

Maintenance

ActivityInactive
ResponsivenessSlow

Resources