| FMRS | 55 / 100 · C | 77 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 |
|---|
| Maintenance | 8 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - Users who want to manage a personal Joplin knowledge base through AI.
- MCP client users who need note, notebook, and tag search and organization.
- Users who need to restrict AI access by notebook path.
| - 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 use Joplin or cannot enable Web Clipper.
- Users who cannot provide a Joplin API authorization token.
- Read-only scenarios where write, update, or import permissions are not desired.
| - 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 | - Requires a running Joplin Web Clipper authorization token supplied through JOPLIN_TOKEN.
- Read permissions cover searching, viewing notebooks and tags, and connectivity checks.
- Write, update, delete, and import operations can be controlled individually through configuration or environment variables.
- Delete operations, retrieving all notes, and file imports are disabled by default.
- notebook_allowlist can restrict read and write access by notebook path.
| - 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 | - After enabling delete, update, or import tools, an AI assistant can modify or delete Joplin content; delete operations are disabled by default.
- Without a notebook allowlist, all notebooks are accessible by default.
- Search results and individual notes can expose content; content_exposure settings control previews and full bodies.
- When exposing HTTP or SSE publicly, operators must configure a reverse proxy and TLS; the documentation recommends a reverse proxy for public exposure.
- The token is a secret credential and should not be exposed or placed in untrusted configuration.
| - 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, Jan AI, OllMCP | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 26 | 26 |
|---|