Skip to main content
Glama
billy12151

memory-arbiter-mcp

by billy12151

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEMORY_ARBITER_CLIENTYesClient identifier for the tool (e.g., zcode, codex, cursor, claude-code)
MEMORY_ARBITER_DB_PATHYesPath to the shared SQLite database file
MEMORY_ARBITER_AGENT_IDYesAgent identifier for the client (e.g., zcode-default)

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
memoryA

Daily memory operations: remember, find, batch_find, read, update, judge, status, help.

workspace is required on remember — discover buckets once with memory_review(view="workspaces") (e.g., at session start) and reuse that list; re-query only when unsure or before deliberately creating a new bucket ('default' is the global pool).

Call memory(action="help") to discover accepted fields, judge requirements, value enums, update modes, and action_required paths before relying on a result that requests attention.

update edits in place: 1..8 local edits use patches=[{old_text,new_text}] (atomic all-or-nothing, one version bump); full rewrites use new_content; a single small edit may use old_text/new_text.

batch_find runs up to 8 queries in one call and returns one merged index page (dedup by memory_id, matched_query_ids per item).

find is an index page: results carry metadata + content_chars + a bounded outline (offsets usable directly as read span starts), not full content — content_mode (v0.15.10, preview default) is a single-choice enum: "hits" adds hit_spans (vector-matched unit text + span coordinates, never truncated; >=50% coverage upgrades an item to full text; hit_window=N (default 0) extends each hit with +/-N neighbouring complete sentences, neighbours marked matched=false; hit_spans appears only on query-recall pages — browse/filter pages carry none; hits whose evidence row lags the memory's current version are dropped with a stale_hit_spans marker plus a re-query warning), "full" returns whole texts. Space-separated short CJK words (each <=4 chars, e.g. "向量 唯一键 冲突") are understood as keywords: semantically close memories whose content/subject contains a keyword rank higher (0.17.0; whole-word matching, generic words ignored). Offsets are 0-based Unicode code-point offsets into the content as indexed for the item's version; the evidence index may lag right after an edit (see vector_lag). Score compares only within the page; if the top page misses, reword the query or add tags_filter instead of deep paging. The size block meters the returned page (tokens_estimate + display_hint).

memory_reviewB

Read-only inspection: overview, doctor, conflicts, conflict_detail, history, expired, audit, entities, workspaces, help.

Use memory_review(view="help") for accepted fields. Inspect conflict_detail before judging a conflict so its members, value groups, revision, and apply state are visible.

memory_governA

Authorized governance: retire, merge near-duplicates, apply/replan/resolve conflicts, confirm, and manage workspaces.

Every state-changing action requires explicit user authorization for that action, then authorized=true. Workspace-mutating actions (confirm_pending_workspace, rename_workspace_canonical, migrate_workspace, separate_workspace_alias, move_memories_workspace) also require workspace — call memory_review(view="workspaces") first to list existing buckets. Call memory_govern(action="help") for exact actions, accepted fields, impact notes, and confirmation semantics.

memory_repairB

Maintenance: evidence rebuild, conflict scans (scheduled-task spec under help topic scheduled_tasks), full-library duplicate sweeps (scan_duplicates), history cleanup, entity assignment, pending activation, backup replay, notices, and semantic runtime control.

Use memory_repair(task="help") for notice handling and semantic_control actions. Semantic notices are advisory; read both memories before dismiss or resolve, and never pass a notice directly to judge or resolve_conflict.

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

Disambiguation4/5

The four tools are mostly separated by lifecycle stage: daily operations, read-only review, authorized governance, and maintenance. There is some conceptual overlap around conflict inspection, judgment, and resolution across memory, memory_review, and memory_govern, but the descriptions define handoffs well enough for an agent to choose correctly.

Naming Consistency5/5

All tool names use lowercase snake_case and share a clear memory_ prefix except the base memory tool. The suffixes review, govern, and repair make each tool's role predictable.

Tool Count5/5

Four top-level tools is appropriately compact for a complex memory-management server. Bundling many sub-actions into each tool avoids tool sprawl while keeping high-level categories distinct.

Completeness5/5

The surface covers memory creation, retrieval, update, review, governance, conflict handling, maintenance, and repair. No obvious lifecycle gaps or dead ends are apparent for the stated memory-arbiter domain.

Maintenance

ActivityActive
ResponsivenessNo issues