| FMRS | 70 / 100 · B | 77 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 |
|---|
| Maintenance | 18 / 20 | 16 / 20 |
|---|
| Documentation | 17 / 20 | 18 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 |
|---|
| Best for | - Privacy-conscious researchers and developers who want to run LLMs and search fully locally
- Users already running local models via Ollama, LM Studio, or llama.cpp
- People who want to give Claude multi-engine academic search and structured report generation
- Local, STDIO-based integration into Claude Desktop or Claude Code
| - 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 | - Multi-user or network-exposed deployments — this MCP server has no built-in authentication or rate limiting and is documented as local-use only
- Users wanting a zero-config tool — it requires configuring an LLM provider and a search engine, and sometimes deploying SearXNG
- Teams needing real-time multi-user collaboration features
| - 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 | - Access to a configured LLM (local endpoint or cloud API key)
- Outbound network access to call configured search engines (arXiv, PubMed, SearXNG, Brave, etc.), unless restricted to local documents only
- Local filesystem read access for analyze_documents to work with private documents
- Read/write access to the local encrypted (SQLCipher) database
| - 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 | - The docs explicitly warn this MCP server is designed for local use only via STDIO transport, has no built-in authentication or rate limiting, and should not be exposed over a network without additional security controls
- Credentials (e.g. API keys) are held in process memory during active sessions, a routine runtime risk the project mitigates with session-scoped credential lifetimes and core dump exclusion
- Research queries are sent to whichever search engines are configured, and cloud LLM providers (OpenAI, Anthropic, Google, etc.) receive query/document content when selected
- Docker's --network host mode can silently fail to expose ports or misroute localhost on Windows/WSL2/Mac
| - 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, Claude Code | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 8 | 26 |
|---|