Skip to main content
Glama
yanglinfeng

Memory Bridge

by yanglinfeng

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEMORY_BRIDGE_USER_IDNoUser ID for the memory bridge. Required — either this or MEMORY_BRIDGE_MCP_TOKEN must be set, otherwise the server refuses to start. The official Docker image already has MEMORY_BRIDGE_USER_ID=default built in, so no configuration is needed when using Docker.
MEMORY_BRIDGE_MCP_TOKENNoMCP token for the memory bridge. Required — either this or MEMORY_BRIDGE_USER_ID must be set, otherwise the server refuses to start.

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
memory_rememberA

保存值得跨会话保留的稳定事实、偏好、项目决定、重要事件或指令。不要保存闲聊、临时状态、密码、令牌或未经用户同意的敏感信息。重复内容会自动合并。

answer_calculatorA

对算术表达式做确定性求值,支持 + - * / % ^ 与括号。召回结果中的数值需要加减乘除(金额合计、单价×数量等)时调用,不要心算。

answer_date_diffA

计算两个日期相差的天数与年/月/日拆分。日期支持 ISO、YYYY/MM/DD、中文(2024年3月5日)。涉及"间隔多少天/多久"的问题时调用。

answer_date_shiftA

把日期平移指定天数(可为负),返回结果日期与星期。"X 天后是几号""提前 N 天"类问题调用。

memory_recallA

回答涉及用户偏好、过去事件、项目状态或既有决定的问题前调用。只返回与当前查询相关的少量长期记忆,并解释命中原因。

memory_get_contextB

在回答用户前检索相关长期记忆,并返回可直接加入模型上下文的紧凑文本。适合每轮对话前调用。

memory_updateA

修改已经存在但不准确、过期或需要补充的记忆。仅提交需要更改的字段;修改 content 时必须写成修正后的完整、独立事实,不要写“用户修正了”之类的过程描述。

memory_forgetA

根据用户明确要求删除一条记忆。采用可恢复的软删除,并保留审计记录。

memory_listB

按条件查看记忆,适合管理、核对或让用户确认系统记住了什么。

memory_statsA

查看长期记忆数量、类型和命名空间分布。

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

Disambiguation4/5

Most tools are clearly distinct: memory_remember/forget/update cover the write lifecycle, while answer_calculator/date_diff/date_shift are unambiguous utility functions. The one real overlap is memory_recall vs memory_get_context, which both retrieve relevant long-term memories and differ mainly in output format, so an agent could occasionally pick the wrong one.

Naming Consistency4/5

Two clear prefix groups (memory_* for 7 tools, answer_* for 3) give a predictable pattern, and snake_case is used throughout. Minor deviations exist: some names are verb-led (memory_forget, memory_update) while others are noun-led (memory_stats, answer_calculator), and memory_get_context is a longer compound, but all remain readable.

Tool Count5/5

Ten tools is well-scoped: seven cover the memory lifecycle and three provide computation helpers that support answering questions from recalled data. Each tool earns its place with no redundant entries.

Completeness4/5

The memory surface covers full CRUD plus listing and stats (remember, recall/get_context, update, forget, list, stats), which is a complete lifecycle. Minor gaps exist around namespace/bulk management and export, and the added calculator/date tools are helpful but arguably outside the core memory domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues