| FMRS | 53 / 100 · D | 77 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 11 / 20 | 15 / 20 |
|---|
| Best for | - Users with OctoPrint, Klipper, Duet, Repetier, Bambu Lab, Prusa, or Creality printers
- Users who want to drive printing and model workflows from an MCP client in natural language
- Technical users needing an end-to-end modify-STL, slice, and print workflow
- Bambu users using FULU OrcaSlicer-bambulab or Bambu Studio as the project slicer
| - 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 any supported printer or printer management system
- Users unwilling to provide printer credentials (API keys, access tokens, serial numbers)
- Users expecting to override slicer settings such as layer height or temperature directly from MCP (must be done before generating the 3MF)
- Users expecting complete real-time streaming Bambu status semantics (status reading remains limited)
- Bambu users without Developer Mode and LAN Only Mode enabled or whose printer is not on the same network
| - 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 | - API key or Bearer token for the printer management system
- Bambu Lab serial number (BAMBU_SERIAL) and access token (BAMBU_TOKEN)
- Network access to the printer's local network (including Bambu MQTT port 8883 and FTPS port 990)
- Read/write access to the local filesystem for STL, G-code, and 3MF files and the temp directory
- Ability to launch external slicer executables (SLICER_PATH) and optionally the FULU bridge command
- Optional MCP_ALLOW_EXECUTABLE_ARG=1 to accept per-call local executable selectors
| - 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 | - STL operations load entire models into memory; large files (e.g., over 10MB) can cause out-of-memory issues
- Bambu file operations may use unsecured plain FTP, exposing transfers to network eavesdropping
- A wrong Bambu model preset (bambu_model) can generate dangerous G-code and cause the bed to crash into the nozzle and damage the printer
- Allowing per-call executable paths (MCP_ALLOW_EXECUTABLE_ARG) lets untrusted input choose which local program runs; enable only for trusted diagnostics
- Tool output should be treated as untrusted input, so prompt injection is a risk and destructive operations should have human confirmation gates
- Credentials are stored as environment variables in client config, so a leak grants printer control
| - 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 Code, Cursor, Codex | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 23 | 26 |
|---|