user-db
Central user-state database MCP server with durable profile facts and live virtual sensors (stress, room intensity) with configurable smoothing, readable by any agent or smart-home service.
README
user-db
Central user-state database as an MCP server: durable profile facts plus live virtual sensors (user stress level, room intensity) with configurable smoothing — readable in real time by any agent or smart-home service.
Data separation (important)
This repository contains software only. All personal data lives outside
the repo, in the directory given by USER_DB_DIR (default ~/.config/user-db/):
| File | Content | Written by |
|---|---|---|
profile.json |
durable user facts (name, speech id, birthday, profession, expertise, traits, ...) | you / agents via profile_set |
config.json |
sensor + curve configuration (reactiveness tuning) | you |
state.json |
live sensor state | this software |
Nothing in this repo ever contains user data; examples/ holds neutral
templates. Copy them to USER_DB_DIR to get started:
mkdir -p ~/.config/user-db
cp examples/*.json ~/.config/user-db/
Install & run
python3 -m venv .venv && .venv/bin/pip install mcp
claude mcp add --scope user user-db -- $PWD/.venv/bin/python $PWD/server.py
CLI (same core, for shell loops and Home Assistant command_line sensors):
bin/userdb profile
bin/userdb sensor report stress 70
bin/userdb sensor read stress
bin/userdb state
MCP tools
profile_get/profile_set(field, value)— the user's durable state.sensor_read(name)/sensor_report(name, value)— virtual sensors.state_get— all sensors + the curve combining both axes.
Virtual sensors & reactiveness
A sensor value is not a plain variable. Producers report raw observations (0–100); the stored value follows them via time-aware exponential smoothing:
alpha = 1 - exp(-dt / tau_seconds)
value += alpha * (raw - value)
tau_seconds per sensor in config.json is the reactiveness: small tau =
reactive, large tau = inert. This keeps the sensor from jumping and lets you
fine-tune it for smart-home automations. The first report initialises the
value directly.
Default sensors: stress (the user's stress level, reported by a
watchdog/perception agent) and room_intensity (the room's current scene
intensity, reported by a scene-analysis agent — see
docs/neuronal-interceptor.md).
The two axes & the curve
The system has two orthogonal axes: user stress and room intensity.
A freely definable piecewise-linear curve in config.json maps stress to a
target room intensity:
"curve": {"x": "stress", "y": "room_intensity",
"points": [[0, 85], [40, 60], [70, 35], [100, 15]]}
state_get evaluates it and returns target and delta (actual − target) —
the basis for smart-home decisions ("the user is stressed but the room is
loud → calm it down").
Home Assistant
Expose the smoothed value as a command_line sensor, or bridge it through an
existing MCP that already abstracts Home Assistant:
sensor:
- platform: command_line
name: user_stress
command: "/path/to/user-db/bin/userdb sensor read stress | jq .value"
scan_interval: 60
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。