Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEMORI_API_KEYYesYour Memori API key
MEMORI_API_URLNoAPI endpointhttps://api.memorilabs.ai/mcp
MEMORI_ENTITY_IDNoStable end-user/entity ID
MEMORI_PROCESS_IDNoProcess/app/workflow ID

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
recallA

Retrieve relevant memories for a given query. Call at the start of user turns to fetch prior context, preferences, and facts.

advanced_augmentationA

Store durable facts and preferences after drafting a response. Call after responding to persist user context across sessions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: one exclusively stores/augments memories after responses, while the other retrieves them at the start of turns. No functional overlap exists between the write and read operations.

Naming Consistency3/5

While both use snake_case, they follow different grammatical patterns: 'recall' is a simple action verb, while 'advanced_augmentation' is an adjective-noun phrase describing a feature. A consistent pair would use matching patterns like 'store_memory' and 'recall_memory' or 'augment' and 'recall'.

Tool Count3/5

Two tools provides the absolute minimum viable surface for a memory system (read/write), but feels thin for the domain. Memory management typically requires additional operations like delete, update, or list, making this borderline for a complete memory server.

Completeness3/5

The server covers basic create (store) and read (recall) operations but lacks update, delete, or enumeration capabilities. Users cannot correct stored memories, remove outdated facts, or browse all stored context, creating notable gaps in the memory lifecycle.

Maintenance

ActivityInactive
ResponsivenessUnresponsive