asmemory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASMEMORY_DB_PATH | No | Path to the SQLite database file. Defaults to ~/.asmemory/memory.db if not set. | |
| ASMEMORY_MCP_PATH | No | Absolute path to the asmemory-mcp command, used instead of installing the command. |
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 |
|---|---|
| memory_store_stateC | 存一条状态事件到记忆库:某实体(entity)在某个指标(metric)上的数值(value),可带单位与标签。 |
| memory_store_actionA | 存一条动作事件:actor 对 object 执行了 verb,可带控制量 amount 与元数据。 |
| memory_trendB | 分析某指标的时间趋势(rising/falling/flat + 斜率)。 |
| memory_anomalyB | 检测某指标的异常点(z-score,|z|>threshold 视为异常)。 |
| memory_causalA | 因果关联:某动作(verb)对某指标(entity.metric)的影响,返回动作前后均值变化量。 |
| memory_summaryB | 记忆库统计摘要:状态数/动作数/实体列表/动作类型列表。 |
| memory_export_datalensA | 导出 DataLens 格式(监控指标+控制手段+红线)的 CSV 与 config,用于可视化优化分析。 |
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 7 tools
Each tool targets a distinct operation—storing state, storing action, trend analysis, anomaly detection, causal analysis, export, and summary. memory_trend and memory_anomaly both analyze metric series, but their purposes are clear enough to avoid real confusion.
All tools share the memory_ prefix and snake_case, which helps consistency. However, the second part mixes noun-style names (trend, anomaly, causal, summary) with verb-object names (export_datalens, store_state, store_action), so the naming convention is readable but not uniform.
Seven tools is well-scoped for a memory and analysis server: two writers, three analyzers, one export, and one summary. There is no obvious redundancy or bloat.
The surface covers state/action ingestion, trend/anomaly/causal analysis, export, and summary. It lacks direct raw-event queries or deletion, but that may be intentional for an append-only memory store, so this is a minor gap rather than a blocker.