In-depth architectural comparison of the MCP Server Docker and Hevy (unofficial) MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Server Docker
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Hevy (unofficial)
Developer Tools · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose MCP Server Docker if you need specialized Developer Tools tools running via a local process. Choose Hevy (unofficial) if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Server Docker when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
MCP Server Docker is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Hevy (unofficial) belongs to Developer Tools using local stdio subprocess. Select MCP Server Docker when you need capabilities focused on developer tools and Hevy (unofficial) when you require tools for developer tools.
List the user's routine folders (id + title). Check this before creating a folder — reuse an existing one when the name matches.
create_routine_folder
Create a routine folder, or return the existing folder if one with this exact title already exists (never duplicates).
list_routines
List the user's existing routines (id, title, folder_id, exercise_count). Use to avoid creating duplicates.
create_routine
create a routine (lb-first: weight_lb snaps to 2.5/5 lb increments; RPE folded into notes; supersets; duration/distance targets supported)
get_workouts
Get the user's most recent logged workouts, newest first, as compact summaries: title, date, duration, and per-exercise set count + top set. Use get_workout for full set-by-set detail of one workout.
get_workout
Get one logged workout with every set (weights in kg). Use the id from get_workouts.
get_workout_count
Total number of workouts the user has ever logged in Hevy.
get_exercise_history
past sets + estimated 1RM in lb for one exercise (full history, optional date range)
get_routine
Get one routine in full (all exercises and sets). Always call this before update_routine so you can send back the complete routine.
update_routine
Replace an existing routine. WARNING: this overwrites the routine — Hevy replaces its exercises with exactly what you send, so first call get_routine and include every exercise you want to keep. Folder cannot be changed here; duration/distance/custom-metric set targets round-trip safely.
get_training_summary
weekly sessions/volume (lb), sets per muscle group, top-lift 1RM trend