plastic-memory-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | Alternative API key recognized for the OpenAI-compatible endpoint (e.g. OpenAI). Optional. | |
| DEEPSEEK_API_KEY | No | Alternative API key recognized for the OpenAI-compatible endpoint (e.g. DeepSeek). Optional. | |
| PLASTIC_MEMORY_HOME | No | Data directory for plastic-memory. Defaults to ~/.plastic-memory/ for standalone MCP/CLI usage; under Hermes it defaults to <hermes home>/plugin-data/plastic-memory/. | |
| PLASTIC_MEMORY_MODEL | No | Model name for the OpenAI-compatible endpoint used for dream distillation, e.g. deepseek-chat. Optional. | |
| PLASTIC_MEMORY_API_KEY | No | API key for an OpenAI-compatible endpoint used for dream distillation. Optional; without it, distillation falls back to a rule-based mode. | |
| PLASTIC_MEMORY_BASE_URL | No | Base URL for the OpenAI-compatible endpoint used for dream distillation, e.g. https://api.deepseek.com/v1. Optional. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pm_statusA | 可塑性记忆的健康度与容量:三层各有多少条、被拦下多少杂讯、做过几次梦。只返回数字,不返回核心印象的内容。 |
| pm_recallA | 在事件层里按语义检索旧事(用户说过的话、被记下的关键事件)。用于需要具体细节时;核心印象层不通过这个工具暴露。 |
| pm_observeA | 显式记下一件事。日常对话会自动观察,只有当你判断某句话重要到必须落盘时才手动调用。 |
| pm_dreamB | 立刻做一次梦(离线巩固):按主题把事件合并成判断、检出矛盾、淘汰衰减到阈值的杂事。返回本次的操作计数。 |
| pm_personaA | 查看当前的人设面与权重。可以给一段假设的话,预演它会激活哪几面、是否进入交叉态。 |
| pm_compactA | 半衰期压缩:核心区太满、快要挤掉重要的东西时,把大部分印象交给梦做二次压缩,合并成更少的几条判断。必须先跟用户讲清楚(会丢掉一些细节)并得到同意,confirm=true 才执行。旧条目不删除,只是退出常驻,仍可追溯。 |
| pm_traceA | 追溯一条印象是怎么来的:它由哪几句原话压出来、或者由哪几条旧印象再压出来的。用于自查『我为什么记得这件事』,也用于确认梦有没有编造。 |
| pm_pinA | 把一条记忆钉住(或取消钉住)。钉住的不受半衰期影响、不参与常驻轮换,永远在注入里。用于婚丧嫁娶、承诺、健康、钱、法律这类只提一次但后果很大的事。 |
| pm_diaryA | 把核心印象写成一篇日记交给用户。核心区平时不对用户开放,这是唯一的出口——只在用户明确要求、或临别/迁移时用。输出是叙事,不是条目清单。 |
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 9 tools
The tools mostly target distinct memory operations: observe, recall, pin, trace, status, diary, persona, dream, and compact. The only notable overlap is pm_dream and pm_compact, since both perform consolidation/compression, though the descriptions distinguish immediate dreaming from core-area overflow compression with user consent.
All tools use the same pm_ prefix followed by a single lowercase verb or noun in snake_case: pm_pin, pm_diary, pm_status, pm_recall, pm_observe, pm_dream, pm_persona, pm_compact, pm_trace. The pattern is predictable and consistent throughout.
Nine tools is well-scoped for a memory/persona management server. Each tool corresponds to a meaningful operation in the memory lifecycle, and none appears redundant or trivial.
The surface covers observation, retrieval, pinning, tracing, status, diary export, persona inspection, dreaming, and compaction, which is a coherent lifecycle. Minor gaps remain around explicit memory editing or targeted deletion/forgetting, but the system's design suggests decay and compression handle removal indirectly.