Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AETHER_PORTNoThe port the Aether Cache engine listens on. Set this if port 7380 is taken, then run `aether-cache setup` again.7380

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
rememberA

Save a durable fact about this project so future sessions, in any AI tool, know it. Use this, not a built-in memory or notes file, whenever the user asks you to remember something about the project.

Good facts: conventions ("we use pnpm, not npm"), setup gotchas ("tests need DOCKER_HOST set"),
decisions and their reasons. Not: temporary task details or anything in the code already.
files: repo-relative paths this fact depends on (e.g. ["docker-compose.yml"]), so the memory
can be flagged when those files change.
recallA

Search this project's shared memory by meaning. Call it at the start of every task, and whenever project-specific knowledge (setup, conventions, past decisions) might matter. Only current (active) memories are returned; outdated or replaced ones are skipped.

explain_memoryA

Show where a memory came from (which tool and session saved it, which files it's linked to) and everything that has happened to it since. Use it when a memory looks wrong or surprising.

mark_outdatedA

Mark a memory as no longer true, with a short reason. It stops showing up in recall but keeps its history, so you can still see what it said and why it was retired.

replace_memoryA

Retire an older memory because a newer one replaces it (e.g. "we use Postgres" replaced by "we migrated to MySQL"). The old memory stops showing up in recall but keeps its history.

check_staleA

Check whether any memory's linked files have changed since it was saved, and retire those memories. recall already does this automatically; call it directly after big changes.

confirm_memoryA

Mark a memory as still true (e.g. after it was retired because a linked file changed, but the fact itself didn't). Re-links it to the current version of its files.

sync_to_filesA

Write this project's current memories into the managed section of AGENTS.md / CLAUDE.md, so they're committed with the code: teammates and tools without Aether Cache see them, and changes show up in reviews. Call it when the user asks, or after a batch of new memories.

list_conflictsA

List pairs of memories in this project that may contradict each other and need a decision.

resolve_conflictA

Settle a possible conflict. replaces_old=True: the new memory replaces the old one (the old one is retired). replaces_old=False: both are true, keep both. Ask the user if you're not sure.

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 10 tools

Disambiguation4/5

Most tools have distinct purposes (create, read, inspect, sync, conflict management), but there is a cluster of retirement-oriented tools (mark_outdated, replace_memory, check_stale, resolve_conflict) that could be confused at a glance. Detailed descriptions mitigate the overlap, so an agent can usually select correctly.

Naming Consistency4/5

The set is predominantly verb_noun in snake_case (explain_memory, mark_outdated, replace_memory, check_stale, confirm_memory, sync_to_files, list_conflicts, resolve_conflict), but two foundational tools (remember, recall) are bare verbs. This is a minor deviation that remains readable and largely predictable.

Tool Count5/5

With 10 tools, the set is well-scoped for project memory management. Each tool serves a clear role across creation, retrieval, lifecycle, and conflict resolution, and no tool feels redundant or missing.

Completeness4/5

The lifecycle is well covered: create, search, inspect provenance, retire, replace, confirm, sync, and resolve conflicts. However, there is no explicit hard-delete or purge operation, and no direct way to list all memories without a semantic search, which are minor gaps for the domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues