Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEMEX_VAULTYesAbsolute path to the Memex vault directory (its own git repo) that the MCP server reads and writes.

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
rememberA

Save or update a note in the user's persistent memory. Re-using a title updates that note. Pass a stable key for a fact that should have one current value (e.g. 'storage-choice'); if a different active note already holds a different value for that key, the result warns you. If the project already uses a different-but-similar key, the result nudges you to reuse it. To replace an older note on purpose, add a line 'Supersedes: [[old-id]]' to the body.

recallA

Search memory. Returns up to 8 ranked hits as title, id and a short snippet. Use read_note for the full text.

read_noteC

Read one note's full body by id.

get_backlinksA

List the notes that link to the given note id via [[wikilinks]].

list_notesB

List notes (id, title, project, tags), optionally filtered by project and/or tag.

list_tagsB

List tags with note counts, optionally within one project.

resolve_conflictA

Resolve a contradiction between two notes (ids from a remember WARNING, or the Conflicts page). Only do this when the user has told you which side is right; if unsure, ask them. a is the older note, b the newer. Actions: keep_a (b is marked superseded), keep_b (a is marked superseded), or keep_both (requires note, a reconciliation explaining how both hold; both stay active). Each resolution is exactly one git commit. Nothing is deleted.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a distinct role: read_note (fetch full body by id) vs recall (ranked snippet search), list_notes vs list_tags (different resources), and remember (write/update) vs resolve_conflict (deliberate contradiction workflow). The descriptions explicitly cross-reference each other (recall says 'use read_note for the full text'; remember's warnings feed resolve_conflict), so an agent can pick correctly.

Naming Consistency4/5

Four tools follow a verb_noun pattern (read_note, get_backlinks, list_notes, list_tags) and all names are uniformly snake_case. The three memory-lifecycle tools use bare verbs (remember, recall, resolve_conflict), which is a minor but readable deviation rather than inconsistency.

Tool Count5/5

Seven tools is well-scoped for a personal notes/memory server, and each earns its place: read, write, search, list, list tags, backlinks, and conflict resolution. No redundant or filler tools are present.

Completeness4/5

The surface covers the full read/write/search/update lifecycle plus backlinks and explicit conflict resolution, with supersede semantics substituting for deletion. Minor gaps remain: there is no 'forget'/delete operation at all, and no way to list a note's outgoing links (only backlinks), which agents may want for graph navigation.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues