Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEMALYZE_DBNoSQLite database path./memalyze.db
MEMALYZE_ACTORNoActor recorded in auditlocal
MEMALYZE_AUDITNoWhether to append audit rowson
MEMALYZE_TENANTNoDefault tenant for tool callsdefault
MEMALYZE_HTTP_ADDRNoHTTP listen address, e.g. :8080 for Streamable HTTP; empty means stdio
MEMALYZE_HTTP_TOKENNoBearer token for HTTP; required when binding off-loopback
MEMALYZE_KEEP_ALIVENoOllama model residency30m
MEMALYZE_OLLAMA_URLNoLocal embedding endpointhttp://127.0.0.1:11434
MEMALYZE_EMBED_MODELNoEmbedding modelqwen3-embedding:0.6b
MEMALYZE_REDACT_MODENoRedaction mode: enforce, dry-run, or offenforce
MEMALYZE_REDACT_RULESNoPath to a JSON rule pack; defaults to built-in rules(built-in)
MEMALYZE_QUERY_TIMEOUTNoVector-path budget before degrading3s
MEMALYZE_AUDIT_QUERY_PLAINNoStore query text in audit; by default only SHA-256 and length are storedoff

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

Tools

Functions exposed to the LLM to take actions

NameDescription
echoA

Echo the given text back unchanged. Used to verify the MCP wiring.

memory_addA

Store a memory for later retrieval. Returns duplicate=true when identical content already exists (no new record), and embedding_failed=true when the memory was saved but vectorization failed (keyword search still works).

memory_deleteA

Soft-delete a memory by id. Already-deleted ids are idempotent; an unknown id returns an error instead of pretending to succeed.

memory_searchA

Search memories with vector search first and keyword fallback. degraded=true means the vector path was unavailable; degrade_reason explains why. An empty query lists recent memories.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: echo is a wiring check, while memory_add, memory_delete, and memory_search map to separate lifecycle operations on a single resource. Descriptions reinforce the boundaries (e.g., soft-delete vs. store vs. hybrid search).

Naming Consistency4/5

The three core tools follow a clean memory_verb snake_case pattern. echo is the only deviation, but as a conventional diagnostic utility it does not create confusion.

Tool Count4/5

Four tools is slim but reasonable for a focused memory store; each earns its place except arguably echo, which is a wiring diagnostic rather than a memory operation. Not thin enough to be a mismatch.

Completeness4/5

Add, search (with list-recent fallback), and delete cover the core lifecycle, but there is no get-by-id or update/edit operation, so an agent cannot correct or inspect a specific memory without going through search. These are minor workaround-able gaps assuming memories are effectively immutable.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues