mcp-3D-printer-server — 3D Printer MCP Bridge

Main

• Treat it as an agent-facing control plane: expose safe tools like temperature setting, file inspection, slicing, and printing behind a single MCP server.

• Start with read-only diagnostics and model inspection; enable slicing and print actions only after you’ve validated printer settings and permissions.

• If you containerize, follow the README notes about slicers: host-installed slicers may not work inside Docker unless installed in the image.

Source-backed notes

• README lists capabilities including STL manipulation/analysis, slicing to G-code, and printer control across multiple printer types.
• README install section shows npm install -g mcp-3d-printer-server and a from-source flow using npm link.
• README includes Docker instructions and explains slicer limitations in containerized setups.

FAQ

• Which printer types are supported?: README lists multiple backends (OctoPrint/Klipper/Bambu and more); confirm via config options.
• Can it run without a slicer?: Some tools are inspection/control; slicing tools require a slicer configured via env vars.
• How do I avoid unsafe prints?: Keep destructive tools behind explicit confirmations in your agent prompt and validate env config before enabling print calls.