| FMRS | 57 / 100 · C | 77 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 13 / 20 | 16 / 20 |
|---|
| Maintenance | 10 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 |
|---|
| Best for | - Job seekers who want to self-host and control their career data.
- Users who want to record jobs or interview questions without leaving an AI chat.
- Users of AI clients such as Claude Desktop, OpenClaw, or Hermes.
| - 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 expecting the MCP server to provide full job search, task, or activity-management capabilities; the README does not document those MCP capabilities.
- Users unwilling to grant an AI client permission to write job applications or Question Bank entries.
- Users seeking a hosted third-party integration without deploying JobSync themselves.
| - 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 the self-hosted JobSync /api/mcp endpoint.
- A Bearer access token generated under Settings > MCP Access.
- With user approval, the ability to add job applications and Question Bank entries and resolve or create related companies, titles, locations, and tags.
- When a default resume and sufficiently substantial job description are available, the ability to save a job-match result based on that resume.
| - 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 access token is shown only once; exposure could allow others to access the MCP endpoint.
- AI-generated matching scores, recommendations, and written content require human review.
- Job-posting text is treated as untrusted input, but users should still inspect confirmation-card details before saving.
- Cloud AI providers introduce different privacy considerations from running models locally with Ollama.
| - 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, OpenClaw, Hermes | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 0 | 26 |
|---|