| FMRS | 49 / 100 · D | 77 / 100 · B |
|---|
| Reliability | 7 / 20 | 12 / 20 |
|---|
| Security and permissions | 4 / 20 | 16 / 20 |
|---|
| Maintenance | 9 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - IT service desk staff and administrators with access to a ServiceNow instance
- ServiceNow admins/developers who want conversational control over change management, catalog building, or knowledge base work
- Teams wanting to automate agile project tracking (stories/epics/tasks) inside ServiceNow via Claude
| - 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 without a ServiceNow instance or valid credentials
- Scenarios requiring strictly read-only access — the default 'full' tool package grants full create/update/delete permissions
- Enterprises needing official ServiceNow vendor support or SLAs (this is a third-party community project, not an official ServiceNow product)
| - 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 | - ServiceNow instance URL and an account with read/write access to relevant tables (incident, change_request, sc_cat_item, kb_knowledge, sys_user, sys_user_group, sys_script_include, workflow, sys_update_set, etc.)
- Basic auth username/password, OR OAuth client ID/secret, OR an API key (one authentication method)
- Local filesystem access to read the .env file storing credentials
| - 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 default 'full' tool package grants create, update, and even delete access across incidents, changes, catalog, knowledge base, and users/groups — misuse could modify or destroy production data
- Credentials are stored in plaintext in the .env file or Claude Desktop config, creating exposure risk
- Tools like approve_change, reject_change, publish_changeset, and publish_article directly affect live ServiceNow processes and visibility, and should be granted carefully
- The SSE server listens on 0.0.0.0 by default, which could allow unauthorized access without proper network isolation
| - 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 Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 76 | 26 |
|---|