Skip to main content
Glama
udjin-labs
by udjin-labs

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OLLAMA_HOSTNoOllama server URL for Ollama embeddings and LLMhttp://localhost:11434
GEMINI_API_KEYNoGoogle Generative AI key for Gemini embedding and Gemini Flash LLM
MNEMOSTACK_LLMNoLLM provider for answer generation and reranking
MNEMOSTACK_PROVIDERNoEmbedding provider for CLI/HTTP/MCP
MNEMOSTACK_GRAPH_URINoMemgraph bolt URI for graph retriever and GraphStore
MNEMOSTACK_BM25_PATHSNoBM25 corpus paths separated by os.pathsep (':' on Unix) for BM25 retriever
MNEMOSTACK_COLLECTIONNoQdrant collection namemnemostack
MNEMOSTACK_QDRANT_URLNoQdrant server URL for remote Qdranthttp://localhost:6333
MNEMOSTACK_LLM_PROVIDERNoAlternative LLM provider (alias for MNEMOSTACK_LLM)
MNEMOSTACK_MEMGRAPH_URINoAlternative Memgraph bolt URI (alias for MNEMOSTACK_GRAPH_URI)
MNEMOSTACK_AUTO_RECORD_IORNoToggle for HTTP recall exposure logging (true/false)
MNEMOSTACK_EMBEDDING_PROVIDERNoAlternative embedding provider (alias for MNEMOSTACK_PROVIDER)

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
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
mnemostack_healthA

Check health of all mnemostack components.

Read-only, no side effects, no authentication required. Returns a JSON object with ok (bool) and per-component status for the embedding provider, Qdrant vector store, and optional Memgraph graph database. Use this to verify the memory backend is reachable before issuing recall queries.

mnemostack_searchA

Search indexed memories with hybrid recall.

Read-only, no side effects, no authentication required. Use this when you need raw memory matches rather than a synthesized answer. Returns a JSON object with ok, query, count, results, tokens_estimate (estimated total text tokens of the results), notes (the AUTHORITATIVE list of routine signals for stages that did not apply — e.g. temporal:no_parse on any query without a date; NOT a fault), and degraded (components that actually fell back, plus a deprecated back-compat duplicate of the routine tags until the next major; an entry absent from notes is a real fault). Results are ranked by reciprocal rank fusion of BM25, semantic, graph, and temporal retrievers when configured; each result includes id, text, score, sources, and payload. Stale facts (invalidated_at set) are hidden by default; use include_invalidated or as_of to see them.

mnemostack_answerA

Answer a question using retrieved memories.

Read-only, no side effects, no authentication required. Use this when you want a concise factual answer synthesized from memory search results instead of the raw matches returned by mnemostack_search. Returns a JSON object with ok, query, answer text, confidence (0.0-1.0), sources, notes (the AUTHORITATIVE routine signals — e.g. temporal:no_parse on any query without a date; NOT a fault), degraded (components that actually fell back, plus a deprecated back-compat duplicate of the routine tags until the next major), fallback_recommended, tokens_estimate (estimated text tokens of the context memories), tokens_used (LLM-provider-reported usage for the answer call; null when unreported), and error. Stale facts are hidden by default; use include_invalidated or as_of to see them.

mnemostack_resolveA

Verify a citation: resolve a chunk id back to its source document.

Re-reads the CURRENT source and returns an honest verdict: intact / source_changed / moved (citation still supported), changed / missing (not supported by the current source), or unresolvable (cannot be verified from this process). Includes the snapshot-hash comparison and the fragment when locatable. Read-only; never mutates stored memory; runs outside the recall path. Resolution is confined to the corpus root recorded at ingest — there is deliberately no way for a caller to point it at another directory.

mnemostack_invalidateA

Mark memories stale by id, non-destructively.

A write tool (parallel to mnemostack_graph_add_triple). Sets invalidated_at (and optionally valid_until) on each point's payload without deleting or re-embedding it; invalidated facts drop out of default recall but stay reachable via include_invalidated / as_of. Points that do not exist are skipped. Pass index_root in multi-root collections to avoid marking another root's chunks stale. Returns ok, requested, and invalidated (the number of points actually updated).

mnemostack_rememberA

Store a memory for the caller's tenant (the write counterpart of mnemostack_search).

A write tool: requires the write scope, embeds server-side, and stamps the process key's tenant so the memory lands in — and is recallable from — exactly this tenant's scope. Ids are deterministic from (source, offset, text): retries and repeated content return duplicate without a second embedding call. Long documents pass chunk=true and yield one result per chunk. Use mnemostack_invalidate to retract a stored memory.

mnemostack_feedbackA

Record explicit feedback for stateful recall learning.

Use signal='clicked' to also record inhibition-of-return exposure. Pass retriever labels from mnemostack_search results as sources so Q-learning can update source weights.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct role: health checks backend status, search returns raw matches, answer synthesizes an answer, resolve verifies citations, invalidate retracts memories, remember stores new memories, and feedback records learning signals. The only potentially confusing pair is search vs. answer, but the descriptions explicitly separate raw retrieval from synthesized response.

Naming Consistency4/5

All tools share the consistent mnemostack_ prefix and mostly use verb-like action names such as search, answer, resolve, invalidate, and remember. health and feedback are noun-style rather than verb-style, which is a minor deviation from an otherwise uniform pattern.

Tool Count5/5

Seven tools is a well-scoped size for a memory server covering health, ingestion, retrieval, synthesis, retraction, citation verification, and feedback. Each tool earns its place without redundancy or bloat.

Completeness4/5

The core memory lifecycle is covered: store with remember, retrieve with search/answer, retract with invalidate, verify with resolve, and learn with feedback. However, there is no permanent delete operation, and the invalidate description references a mnemostack_graph_add_triple write tool that is not present in the set, leaving graph-write coverage unclear.

Maintenance

ActivityActive
ResponsivenessUnresponsive