Hevy MCP Server (chrisdoc) — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Recheck a specific changing behavior of github.com/chrisdoc/hevy-mcp: Has the project clarified remote OAuth versus API-key auth and default telemetry of training data?

Reviewed Oct 9, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Workout history and training routine management

What we know

Community Hevy MCP implementation published at github.com/chrisdoc/hevy-mcp; enables AI-client access to workout and routine data through its documented API integration.

Maintenance / activity evidence

The chrisdoc/hevy-mcp repository released hevy-mcp@5.1.0 on 2026-08-05.

Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Workout/routine information access; potential mutations must be evaluated against chrisdoc/hevy-mcp tool list, not Yurzs/hevy-mcp. Reported action classes: Workout/routine updates: exact tool list not verified for chrisdoc implementation. Complete write authority is not verified.
Authentication not yet verified.
Personal workout/routine records may be read and changed through authorized tools. Body measurements are supported in documented releases. Check telemetry and auth paths for selected local/hosted runtime.

Personal workout/routine records may be read and changed through authorized tools. Body measurements are supported in documented releases. Check telemetry and auth paths for selected local/hosted runtime.
Advisory/security review not completed; no safety badge.
Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Do not mark them as confirmed documented write inventory.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

507 shared-repository stars · 200.5k package downloads / 30 days

Stars observed Oct 9, 2026. Downloads observed Oct 9, 2026.

Repository total for chrisdoc/hevy-mcp; not package-specific.

Exact npm package hevy-mcp; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

Has the project clarified remote OAuth versus API-key auth and default telemetry of training data?

No identified material blocker to an accurately qualified public tracking entry in the limited cited evidence. This is not an installation safety certification; product-specific cautions must remain visible.

Personal workout/routine records may be read and changed through authorized tools. Body measurements are supported in documented releases. Check telemetry and auth paths for selected local/hosted runtime.
Advisory/security review not completed; no safety badge.
Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Do not mark them as confirmed documented write inventory.
Workout/routine information access; potential mutations must be evaluated against chrisdoc/hevy-mcp tool list, not Yurzs/hevy-mcp.
Reviewed write actions: Workout/routine updates: exact tool list not verified for chrisdoc implementation
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Workout/routine writes modify personal fitness records; the project documents error and performance telemetry, and transport depends on runtime/version.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.
Release evidence proves attributable activity, not entire installation or tool-level safety.
Current Discovery source binding and atomic apply must be generated using MCP100 existing pipeline.
data retention and permission scope
exact authentication contract
exact chrisdoc tool write inventory
first-party data processing and retention
remote authentication compatibility
verified Hevy API environment variable
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Do not merge this Node implementation with Yurzs/hevy-mcp Python implementation.
Hevy account/API access may be required.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Original activity observations

The chrisdoc/hevy-mcp repository released hevy-mcp@5.1.0 on 2026-08-05.

Technical identity

github.com/chrisdoc/hevy-mcp

Exact implementation source: https://github.com/chrisdoc/hevy-mcp ↗
Reviewed resource type: MCP Server
Repository identity: chrisdoc/hevy-mcp
Package identity: npm:hevy-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

GitHub repository ↗
chrisdoc/hevy-mcp
Recorded repository material and project history.
Includes references whose attribution is not established.

Setup · Watchlist

Connect remote MCP service

Codex

Publisher instructions with a documented client setup path.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Warning

The key must be available to the Codex process, not merely referenced by name in an MCP config.
Key revocation is separate from removal of the MCP entry; publisher requires Hevy PRO for API access.
Use actual key only in your own secure shell/session, never in project history or public config; ensure Codex starts from this environment.
Run the removal command in the same client and configuration scope used for registration; this does not uninstall an application, revoke third-party authorization, or delete data.
Registering a bearer-token env var name does not set its value.
Exact vendor-specific credential revoke procedure not established from checked official Setup documentation; may be external or not applicable. Do not invent.
MCP100 client-scope note: this Codex CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry. Replace the supplied angle-bracket placeholders privately before using this template; keep credentials out of shell history and shared configuration.
MCP100 client-scope note: this Codex CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry. Run the removal command in the same client and configuration scope used for registration; this does not uninstall an application, revoke third-party authorization, or delete data.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
codex mcp add hevy --env HEVY_API_KEY=<YOUR_KEY> -- npx -y hevy-mcp
Configure / authenticate
Publisher instructions
Requires Hevy PRO/API key; alternatively remote HTTP https://mcp.hevy-mcp.dev/mcp with Bearer auth.
Check connection
Suggested check
Ask for the connected Hevy account or recent workouts (read-only).
Remove / uninstall / revoke
MCP100 setup guide
`codex mcp remove hevy` removes the Codex registration; for other hosts delete the `hevy` configuration.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
codex mcp remove hevy

Official Documentation & Sources

What it does

Community Hevy MCP implementation published at github.com/chrisdoc/hevy-mcp; enables AI-client access to workout and routine data through its documented API integration.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Sports & Entertainment
Best fit: Workout history and training routine management

Representative uses

Workout analysis
routine search
create/update workouts
body measurement

Limitations

Do not merge this Node implementation with Yurzs/hevy-mcp Python implementation.
Hevy account/API access may be required.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Workout/routine information access; potential mutations must be evaluated against chrisdoc/hevy-mcp tool list, not Yurzs/hevy-mcp.
Data handling: Not documented in the reviewed sources
Cost: unknown
Risk and cautions: Personal workout/routine records may be read and changed through authorized tools. Body measurements are supported in documented releases. Check telemetry and auth paths for selected local/hosted runtime.

Access scope and cautions

Write actions: Not verified Workout/routine updates: exact tool list not verified for chrisdoc implementation
Risk level: high
Security notes: Advisory/security review not completed; no safety badge. Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Do not mark them as confirmed documented write inventory.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Workout analysis; routine search; create/update workouts; body measurement.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded transport: stdio. Client notes: Do not assume a particular tool name prefix; inspect tools/list after launch. Project documents OpenTelemetry and error reporting; review telemetry configuration before submitting sensitive data. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Hevy API key for API-backed operations. Exact remote OAuth capability for this implementation not established.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Workout/routine updates: exact tool list not verified for chrisdoc implementation. Recorded permission context: Workout/routine information access; potential mutations must be evaluated against chrisdoc/hevy-mcp tool list, not Yurzs/hevy-mcp.

What limitations and risks should I check before use?

Personal workout/routine records may be read and changed through authorized tools. Body measurements are supported in documented releases. Check telemetry and auth paths for selected local/hosted runtime. This Node implementation is distinct from the Yurzs/hevy-mcp Python implementation. Hevy account/API access may be required. Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode. Advisory/security review not completed; no safety badge. Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Workout/routine writes modify personal fitness records; the project documents error and performance telemetry, and transport depends on runtime/version. Unknown vulnerabilities and provider data handling are not certified by this public tracking review.