GoodMemory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOODMEMORY_USER_ID | Yes | User ID for this memory scope. Required. Can also be passed as --user-id flag. | |
| GOODMEMORY_STORAGE_URL | No | Optional external storage URL (e.g., Postgres). If unset, uses local SQLite. | |
| GOODMEMORY_MCP_ALLOW_WRITE | No | Set to 1 to enable the goodmemory_remember write tool. Default is unset (no write tool). |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| goodmemory_get_contextB | Fetch a compact memory context fragment for a specific question about this workspace. Call it when hook-injected context is missing or insufficient, or when you need memory for a different question than the current prompt. |
| goodmemory_inspect_memoryA | Diagnostic (beyond the primary goodmemory_get_context / goodmemory_remember tools). Use this when you need a read-only snapshot of durable and runtime GoodMemory state for the current workspace. |
| goodmemory_trace_recallA | Diagnostic. Explain a recall: routing, hits, per-candidate scores, and suppression reasons. Call it when a memory that should exist did not surface, or when a surfaced memory looks wrong. |
| goodmemory_search_indexA | Advanced recall (past goodmemory_get_context). Progressive GoodMemory recall step 1: fetch a compact recordRef index for a query, then call goodmemory_get_records for detail. Prefer this over goodmemory_get_context when you need specific records rather than a rendered summary. |
| goodmemory_timelineA | Advanced recall. Use this for progressive GoodMemory recall when you need compact chronological context before drilling into recordRefs. |
| goodmemory_get_recordsA | Advanced recall. Use this for progressive GoodMemory recall after search_index or timeline returns recordRefs that need detail. |
| goodmemory_read_artifactsB | Diagnostic. Use this when you need the accepted host-adapter artifact projection for the current workspace. |
| goodmemory_statsA | Diagnostic. Record counts and runtime metadata (embedding/retrieval status via the |
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
- 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/hjqcan/GoodMemory'
If you have feedback or need assistance with the MCP directory API, please join our Discord server