Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AWS_PROFILENoS3 credentials profilevms-holdings
DJ_MEMORY_HOMENoHot source repository root~/.local/dj-memory
DJ_MEMORY_USERNAMENoS3 key prefix (s3://bucket/{username}/)OS user
DJ_MEMORY_NEO4J_URLNoKnowledge graphbolt://127.0.0.1:7687
DJ_MEMORY_S3_BUCKETNoCold storage bucketvms-memory-mcp
DJ_MEMORY_S3_REGIONNoBucket region — does not inherit the profile default regionap-northeast-2
DJ_MEMORY_LISTEN_ADDRNoBind address (loopback fixed)127.0.0.1:8420
DJ_MEMORY_OPENSEARCH_URLNoEpisodic indexhttp://127.0.0.1:9200
DJ_MEMORY_EPISODIC_TTL_DAYSNoDays after which consolidated episodes move to cold storage30

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
memory_rememberA

Create a memory (markdown original + derived index). Returns possible_conflicts with judgment material (shared entities, age gap, latest_wins_eligible) — the caller judges: supersede, keep both, or correct itself. Nothing is ever overwritten automatically. Identical content is idempotent (returns the existing id).

memory_recallA

Hybrid lexical search (word/trigram FTS + CJK-aware fallbacks). Returns paths, excerpts, and score components — read the file (or memory_read) for full content; nothing is auto-injected. Ranking: text * trust * state * (1 + freshness + heat); old unused memories sink, never vanish.

memory_readB

Full content plus provenance: frontmatter, supersede chain in both directions, conflicts, usage.

memory_updateA

edit: revise wording/metadata in place (state preserved — meaning-changing revisions should use supersede instead). supersede: id wins over other_id (non-destructive version chain). set_state: explicit lifecycle transition. link: relate two memories. resolve_conflict: record a keep-both judgment for a surfaced pair.

memory_forgetA

archive: sink from default recall (recoverable). deprecate: judged wrong — requires a reason, preserved for opt-in reads. purge: delete the file — only from archived/deprecated and only with confirm=true; if the store is a git repo, history is the backstop.

memory_statusB

The honesty surface: counts by state/type/trust, pending conflict judgments, review-due memories, distillation (compaction) candidates, unparseable files, index freshness, dictionary state.

memory_reindexA

rebuild (default): drop all derivatives and reconstruct them from the memory files — originals own the content, so this is disaster recovery (only usage heat is lost). verify: full re-hash audit that ignores the stat gate and reports drift (files whose content no longer matches the index).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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/drakejin/memory-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server