codex-lcm
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| lcm_statusB | Health and storage status of the codex-lcm memory database. |
| lcm_grepA | FTS5 lexical search with literal substring fallback across messages and summaries. Returns snippets with session and summary references. |
| lcm_recallB | Lexical FTS5 recall with literal substring fallback across retained summaries and raw messages. |
| lcm_expandB | Drill into a summary: for a leaf summary returns its source messages, for a condensed summary returns its parent summaries. |
| lcm_recentC | Recent activity across sessions in a time window. |
| lcm_describeC | Structured metadata for a session or summary. |
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 6 tools
lcm_grep and lcm_recall are nearly indistinguishable: both are described as lexical FTS5 search with literal substring fallback across messages and summaries. The remaining tools are distinct, but this overlap creates a real risk of misselection.
All tools share the lcm_ prefix and snake_case convention, which is highly predictable. Most names are verb-like, though lcm_recent and lcm_status are descriptive/adjectival rather than action verbs.
Six tools is well-scoped for a memory-database access server, covering expansion, recent activity, metadata, health, and search without excessive surface area.
The retrieval surface is fairly complete for reading and inspecting memory, including expansion and health status. However, there is no visible write/ingest operation, so agents cannot persist or update memories through this server.