Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
--dirNoAny other memory directory to use instead of Claude Code’s project memory directory. Add --format claude-code to write Claude Code’s file format there.
--formatNoMemory file format for --dir; use 'claude-code' to write Claude Code’s file format.
RECALL_DIRNoEnvironment variable equivalent of --dir.
--read-onlyNoLet the other agent read memories without changing them.false
--claude-codeNoPath inside the project whose Claude Code memory to serve. Defaults to the current directory.
RECALL_READ_ONLYNoSet to 1 for read-only mode; equivalent to --read-only.0
CLAUDE_CONFIG_DIRNoReplaces ~/.claude when locating Claude Code’s memory directory.
CLAUDE_CODE_PROJECT_DIR_NAMENoNames the project folder next to CLAUDE_CONFIG_DIR when locating Claude Code’s memory directory.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Long-term memory (/memory). Check memory_list at the start of a task and memory_recall what is relevant. This server is read-only.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
memory_listA

List every saved memory with its type and one-line description. Start here to see what is known.

memory_getA

Read one memory in full. Names match file names; "-" and "_" are interchangeable.

memory_recallA

Read the named memories plus the memories they link to with [[wiki-links]], trimmed to a token budget. Unknown names are reported as missing instead of failing.

memory_dueB

List memories old enough that they should be re-confirmed with the person before being relied on.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation4/5

The four tools have mostly distinct roles: list the catalog, get one memory, recall a graph of linked memories, and surface stale memories. memory_get and memory_recall overlap slightly because both read named memories, but recall's link traversal and token budget distinguish it.

Naming Consistency5/5

All tools use the same snake_case memory_ prefix and a short predictable action label. The pattern is consistent across list, get, recall, and due.

Tool Count5/5

Four tools are well-scoped for a read-focused memory recall server. Each tool covers a distinct retrieval need without obvious padding.

Completeness4/5

The surface covers listing, full reading, linked recall, and freshness checks, which are the core recall workflows. Keyword/content search and memory write/update operations are absent, but those may be outside this server's stated scope.

Maintenance

ActivityNo data
ResponsivenessOutdated data