| FMRS | 53 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 10 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 18 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 |
|---|
| Setup experience | 11 / 20 | 14 / 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
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| 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 needing to write to upstream databases (read-only)
- Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
- Users expecting all advanced features without API keys
|
|---|
| 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 internet access to query public biomedical APIs
- Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
- Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
|
|---|
| 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
| - Upstream API rate limits may affect performance
- Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
- Features requiring API keys (e.g., OncoKB) may be incomplete without them
- Local binary installations need regular updates for compatibility
|
|---|
| Supported clients | Claude Desktop, Claude Code, Cursor, Codex | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 23 | 11 |
|---|