| FMRS | 9 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 2 / 20 | 12 / 20 |
|---|
| Security and permissions | 1 / 20 | 16 / 20 |
|---|
| Maintenance | 3 / 20 | 14 / 20 |
|---|
| Documentation | 2 / 20 | 18 / 20 |
|---|
| Setup experience | 1 / 20 | 15 / 20 |
|---|
| Best for | - Endurance athletes (cycling, running, triathlon) seeking professional-level insights.
- Users who prefer self-hosting to have full control over their data.
- Athletes looking for AI guidance that considers a holistic view beyond just power numbers.
| - Individuals or teams who prioritise privacy and offline operation and do not want data leaving the machine
- Users who share memory across multiple MCP clients such as Claude Code, Claude Desktop, Hermes Agent, OpenClaw, Cursor, Codex and Gemini CLI
- Scenarios that need encrypted storage, a hash-chained audit log and verifiable vault migration
- Users who want low-latency recall, a bundled embedding model and no extra LLM calls inside the memory layer
|
|---|
| Not for | - Casual users who do not want to deal with technical setup.
- Individuals who want a simple step counter without multiple platform data collection.
- Users seeking advanced strength training plans for gym workouts, rather than endurance focus.
| - Users who need cloud multi-device sync or a hosted team memory service; moving between machines means locking the vault and copying the file
- Users who expect the server itself to run an LLM that extracts facts and decides what to remember; Compartment explicitly keeps no LLM inside and leaves that to the host model
- Users who cannot keep a passphrase safe or who need a recovery path if it is lost, since Compartment never generates a password, seed or recovery phrase
- Deployments that require network transports such as SSE or streamable-http; this server is stdio only and opens no ports
|
|---|
| Required permissions | - Access to user-authorized third-party fitness platforms (e.g., Strava, Whoop, Oura) to sync data.
- Authentication via OAuth 2.0 to securely access user data.
- Storage and processing of personal health and training data on a self-hosted server or cloud.
| - Read and write the vault file under the user's home directory, by default ~/.compartment/memory.vault, and its sibling settings file
- Access the session directory holding the unlock credential (configurable with COMPARTMENT_SESSION_DIR), which also carries the shared embedding process's Unix socket
- Optionally use the macOS keychain (compartment unlock --keychain is an explicit opt-in, and it survives reboots)
- Write or merge an mcpServers entry into each MCP client's own configuration file, taking a byte-exact backup first
- Install a PostToolUse hook for Claude Code that captures memory files the agent writes
- Serve a read-only dashboard on 127.0.0.1 behind a one-time random URL token
|
|---|
| Risks and side effects | - Privacy risk: Aggregating health data requires access to multiple third-party accounts; if credentials are compromised, there is a risk of data breach.
- Data accuracy: Analysis depends on the accuracy of synced data; sync issues may lead to incorrect recommendations.
- AI errors: AI analysis powered by Gemini may have inaccuracies or misinterpretations, so it should not replace professional medical or coaching advice.
- Dependency on external services: AI and some integrations rely on Google services and third-party API keys; outages may affect functionality.
| - A leaked passphrase means the encrypted content can be decrypted; Compartment generates no recovery phrase and cannot recover a lost passphrase
- Enabling the memory_unlock tool places the passphrase in the model's context, which is why it is off by default
- If a 2FA keyfile is lost, for example a USB stick, the vault cannot be opened even with the passphrase
- `export --plaintext` writes the vault as unencrypted JSONL, so that file must be handled carefully
- Memory content can come from untrusted sources; recall wraps memories with a notice that they are stored data and content can be marked quarantined, but the host agent must still treat memory as data to limit prompt-injection risk
- The capture hook and client integration write into the user's own settings files, although the implementation backs up and merges rather than replacing
|
|---|
| Supported clients | | Claude Desktop, Claude Code, Hermes Agent, OpenClaw, Cursor, VS Code, Codex, Gemini CLI, Cline, Roo Code, Zed, OpenCode, LM Studio, AnythingLLM, BoltAI, Goose, Kiro |
|---|
| Tools | 0 | 14 |
|---|