rekall
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_HOME | No | Base directory for Codex configuration. Defaults to ~/.codex. Used to locate the jobs directory when REKALL_JOBS_DIR is not set. | ~/.codex |
| REKALL_PIPE | No | Pipe name or transport identifier used for tests to deliberately skip the schema subprocess. | |
| CODEX_THREAD_ID | No | The exact current thread ID used by CLI commands when the optional threadId argument is omitted. | |
| REKALL_JOBS_DIR | No | Alternative local journal directory for Rekall jobs. Defaults to $CODEX_HOME/tools/rekall/jobs (or ~/.codex/tools/rekall/jobs when CODEX_HOME is unset). | $CODEX_HOME/tools/rekall/jobs |
| REKALL_CODEX_BINARY | No | Absolute path to the extension-bundled executable to use when Rekall cannot automatically locate a unique one. | |
| REKALL_ALLOW_UNVERIFIED | No | Set to exactly 1 to bypass the extension version verification gate for deliberate compatibility investigation. Any other value disables the override. |
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 |
|---|---|
| probe_compactionB | Read-only: verify access to the owner and runtime state of the specified current Codex VS Code chat. |
| schedule_compactionA | Schedule ONE compaction after this answer. Only when the user authorizes compaction. Optional handoff describes what to keep/summarize and is saved exactly in a per-job file. resume:true explicitly requests ONE subsequent turn with that handoff and nextStep; use only for authorized continuation. Cancels on observed new user input or a stopped turn. Return the handoff in context before finishing. Compaction prompt itself is not overridden. Check status later; no automatic retries. |
| compaction_statusA | Read the local compaction job result. completed requires a new completed contextCompaction event, not just an accepted request. |
| cancel_compactionA | Cancel pending compaction/continuation dispatches for an exact job ID. Already sent requests cannot be undone. Inspect status afterward. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DitriXNew/rekall'
If you have feedback or need assistance with the MCP directory API, please join our Discord server