Skip to main content
Glama
BulbuLbul86

Codex Native Memory

by BulbuLbul86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Codex Native Memory

No user-submitted related servers found.

    Related Servers

    • memtree

      aiagate
      F
      license
      Not graded
      quality
      C
      maintenance
      Collects session JSONL from Codex and Claude Code into local SQLite memory, exposed through MCP with tools for memory context, search, get, put, forget, sleep, and status.
      -
    • codex-substrate-memory by Substrate-memory

      codex-substrate-memoryofficial

      Substrate-memory
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing durable Substrate organizational memory tools, including search, read, query, ingest, remember, and sync. It integrates with Codex to automatically capture completed turns and session boundaries for persistent memory.
      MIT

    • light-agent-memory-mcp-server

      AliYar-Khan
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.
      12
      12 npm
      MIT

    • engram

      TushaeBXN
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent, local-first AI memory across sessions via MCP tools for storing, searching, and retrieving context from past interactions.
      1
      MIT

    • Codex Memory

      zhangtian-123
      A
      license
      B
      quality
      D
      maintenance
      Local Markdown-backed memory tools for Codex and other MCP-capable agents. Exposes durable agent knowledge via CLI and MCP server.
      5
      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.1/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: bootstrap and context handle project loading, import/export manage data transfer, remember/update/forget/notes cover CRUD on pinned items, search queries conversations, and sources lists AI attachments. No two tools overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent pattern: memory_ prefix with snake_case verb_noun (e.g., memory_remember, memory_import_bundle). No mixing of styles or irregular verbs.

    Tool Count4/5

    With 13 tools, the server covers a comprehensive range of memory operations without being bloated. It could potentially add a prune or merge tool, but the current count is well-scoped for a memory system.

    Completeness4/5

    The tool set provides full CRUD for pinned memory items, import/export, session bootstrap/context, search, and health monitoring. Minor gaps exist (e.g., no bulk delete), but the surface covers core workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources