codex-agent-mem
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| db_path | Yes | Path to the SQLite database file | |
| profile | No | MCP runtime profile: minimal, standard, or full | standard |
| read_only | No | Enable read-only mode (blocks mutating tools) | false |
| daemon_url | No | URL for the optional daemon bridge | |
| telemetry_mode | No | Telemetry mode: off, summary, or debug | off |
| sync_project_doc | No | Enable automatic AGENTS.md sync | false |
| idle_timeout_seconds | No | Idle timeout in seconds before the MCP server shuts down | 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mem_searchC | Search stored codex-agent-mem observations for a project or, when provided, one persisted session within that project. |
| mem_getB | Get one stored observation by id. |
| mem_recentB | Return recent observations, optionally scoped to one project or persisted session. |
| mem_note_createB | Create one manual operational memory note that is indexed for mem_search and eligible for context packs. |
| mem_session_listB | List recent persisted sessions/chats for one project so agents can select a scoped continuity lane. |
| mem_scope_resolveD | Resolve a broad project plus optional thread/path hint into persisted session/sub-scope candidates before requesting active context. |
| mem_bootstrap_contextC | Return defensive startup context: resolve scope from optional thread/path hints and avoid project-wide packs for ambiguous containers. |
| mem_project_briefC | Return a compact brief for one project, optionally scoped to one persisted session. |
| mem_open_workA | Return deterministic open work for one project, optionally scoped to one persisted session. |
| mem_completion_checkC | Return a deterministic closure check for one project, optionally scoped to one persisted session. |
| mem_recent_changesA | Return changes since the last stable context sync: new pending items, resolved work, blocker changes, DoD gap changes, and new decisions. |
| mem_scope_guardC | Return compact scope guardrails for one project, optionally scoped to one persisted session. |
| mem_context_packC | Return a compact continuity pack optimized to carry project or persisted-session context forward with fewer tokens. |
| mem_provenanceC | Return audit provenance for one stored observation, including the original turn context. |
| mem_healthB | Return a deterministic health report for one project: duplicates, contradictions, stale items, DoD coverage, and suggestions. |
| mem_health_runtimeA | Return runtime health for this stdio MCP process: pid, uptime, idle timeout, request counts, and exit diagnostics. |
| mem_snapshot_listC | List stored memory snapshots for one project. |
| mem_snapshot_createC | Create a versioned memory snapshot for one project. |
| mem_snapshot_restoreB | Restore one stored snapshot into the generated AGENTS.md continuity block when the project root path is known. |
| mem_policy_listC | List active and inactive memory policies for one project. |
| mem_policy_validateC | Validate one memory policy definition before adding it. |
| mem_policy_addC | Add one memory policy to a project. |
| mem_policy_removeC | Remove one memory policy from a project. |
| mem_inheritance_listB | List inheritance links for one project. |
| mem_inheritance_addC | Add one inheritance link to a project. |
| mem_inheritance_removeB | Remove one inheritance link from a project. |
| mem_repair_proposeA | Return governed repair proposals based on the latest health report for a project. |
| mem_repair_applyC | Apply one supported repair proposal as a derived repair event. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 28 tools
Most tools have clearly distinct purposes, but there is some potential overlap between retrieval tools like mem_get, mem_search, mem_recent, and mem_recent_changes. Descriptions help differentiate them, but the distinctions may still cause confusion.
All tools follow a consistent mem_verb_noun or mem_noun_verb pattern in snake_case, making them predictable and easy to parse. No mixed conventions are present.
28 tools is on the high side, covering a broad set of memory-related operations. While each tool has a defined purpose, the count feels slightly heavy for a single server.
The tool set covers many memory management aspects, but lacks explicit update and delete operations for stored observations (only create via mem_note_create). This creates a notable gap in the typical CRUD lifecycle.