membrain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMBRAIN_HOME | Yes | Path to the .membrain directory used by the membrain MCP server, for example C:/path/to/membrain-lite/.membrain. | |
| PYTHONIOENCODING | No | Python I/O encoding for the MCP server process. The README example sets this to utf-8. | utf-8 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | 记住一句话。「以后用得上」的才写:一个事实、一条偏好、一次决定、一个教训。不要写寒暄,也不要一次写一段长文——一句话一条。 |
| recallA | 按一句话去翻记忆。五路加权(关键词/语义/重要度/新鲜度/图谱),返回最相关的几条,带类型、层级和分数。 |
| briefB | 唤醒时该注入的那一小段:关于主人的几条最硬的记忆。 |
| tickA | 让遗忘走一步(衰减 + 分层 + 归档)。建议一天跑一次或按需调用。 |
| statsA | 看一眼记忆库的规模:总数、各层级条数。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct role: remember writes, recall searches, brief returns a curated wake-up subset, tick runs maintenance, stats reports metrics. The only mild overlap is between recall and brief (both return memories), but the descriptions clearly separate query-driven retrieval from a fixed high-importance digest.
All five names are short, lowercase, single-word tokens with no mixed casing or prefix conventions. There is a slight verb/noun mix (remember/recall/tick vs. brief/stats), but the style is uniform and readable.
Five tools cleanly cover the memory lifecycle: write, retrieve, digest, maintain, and measure. Nothing feels redundant and no operation is split into artificial variants.
The core write/read/maintenance loop is covered, but there is no way to update or delete a specific memory — errors can only be corrected by writing a new memory or waiting for tick decay. This append-only design is plausible but leaves notable gaps for agents needing correction or targeted removal.