| FMRS | 50 / 100 · D | 77 / 100 · B |
|---|
| Reliability | 5 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 |
|---|
| Best for | - Knowledge workers who need to retrieve personal screen and audio history.
- Users who prioritize local processing and privacy.
- Developers who want to provide work context to Claude, Cursor, or other MCP clients.
- Remote workers who need meeting transcription and activity review.
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
|
|---|
| Not for | - Users who do not want continuous screen or audio capture.
- Teams that require centralized cloud storage without local recording.
- Use cases requiring only ordinary file-system or database access.
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
|
|---|
| Required permissions | - Screenpipe needs applicable screen-recording permissions to capture screen content.
- System-audio and microphone capture require the relevant system audio or microphone permissions.
- The application uses the accessibility tree to extract screen text and falls back to OCR when unavailable.
- On macOS, system-audio capture requires Screen & System Audio Recording permission and the relevant experimental feature to be enabled.
| - Requires HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
|
|---|
| Risks and side effects | - Screens, audio, transcripts, and search indexes may contain passwords, private conversations, or proprietary information.
- Data is stored locally by default, but enabled analytics and crash diagnostics may send device or error metadata.
- Cloud transcription, hosted AI, or cloud sync can remotely process related audio, prompts, context, or synchronized data.
- Continuous capture consumes system resources; the README reports typical CPU usage of 5–10%.
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
|
|---|
| Supported clients | Claude Desktop, Cursor, VS Code, Cline, Continue | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 0 | 26 |
|---|