Provides tools for managing Bambu Lab 3D printers, including listing printers, checking AMS filament states, creating print sessions from 3MF/STL files, and starting prints with user approval.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@bambu-gateway-mcp list my printers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server that exposes the bambu-gateway print-session HTTP API to an LLM agent, enabling agent-driven Bambu Lab 3D printer control.
pip install -e .
cp .env.example .env
# Edit .env and set GATEWAY_BASE_URL to your bambu-gateway instanceRelated MCP server: Bambuddy MCP Server
Variable | Default | Description |
| — | URL of the bambu-gateway instance, e.g. |
|
| Whether |
bambu-gateway-mcpThe server listens on stdio and is ready for an MCP client (Claude Code, Cursor, etc.) to connect.
The MCP server exposes the following tools:
list_printers — List configured printers (id, name, machine, online status)
get_ams(printer_id) — Get AMS tray/filament state for filament selection
set_ams_filament(printer_id, ams_id, tray_id, setting_id, tray_color="") — Assign a slicer filament profile to one AMS tray (tray_id is the per-AMS slot 0..3; ams_id=255/tray_id=254 for the external spool)
list_filaments — Available slicer filament profiles
list_processes — Available slicer process profiles
create_print_session(model_path, printer_id, ...) — Configure a print from a local 3MF/STL file. Returns job_id, sliced status, and handoff_url to review/tweak in the browser.
get_print_session(session_id) — Poll session status and handoff_url
start_print(session_id) — Start printing a configured, sliced session (elicitation-gated — asks for approval first)
Call list_printers to pick a target printer
Call get_ams(printer_id) to see filament availability
Call create_print_session(model_path, printer_id, ...) with your 3MF/STL and desired profiles
Share the returned handoff_url with the user to review/adjust in the browser
Once ready, call start_print(session_id) — the server asks for confirmation before printing
start_print asks for explicit user approval in the conversation by default. No print starts silently; the tool prompts for elicitation and only proceeds if the user confirms. Clients that don't support elicitation fail safe (no print).
If your client can't elicit, set REQUIRE_PRINT_CONFIRMATION=false to let start_print print directly (the not-sliced guard still applies). Only do this when you trust the agent driving the printer.
Configure a print from a local model file (.3mf/.stl) on a printer.
Returns {job_id, sliced, handoff_url}. Share handoff_url with the user to review/tweak/print in the browser. Does NOT print. Pass slice=true to pre-slice (so the handoff lands ready-to-print). filament_profiles maps a filament slot index to {"profile_setting_id": ..., "tray_slot": ...}.
Inputs: model_path (required), printer_id (required), slice, copies, +7 more.
Get the AMS tray/filament state for a printer so you can pick tray slots.
Inputs: printer_id (required).
Get a print session's status (incl. whether it's sliced) and handoff_url.
Inputs: session_id (required).
List available slicer filament profiles (for explicit overrides).
Inputs: no named parameters. Returns: result
List the user's configured printers (id, name, machine, default plate, online).
Inputs: no named parameters. Returns: result
List available slicer process profiles (for explicit overrides).
Inputs: no named parameters. Returns: result
Start printing a configured, sliced session — ASKS YOU TO APPROVE FIRST.
Prompts for explicit confirmation in this conversation (elicitation) and only starts the print on an affirmative response. Declines / unsupported clients → nothing is printed.
Inputs: session_id (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Each tool has a clearly distinct purpose: creating sessions, retrieving status, listing resources, and starting prints. No overlap in functionality.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_print_session, list_printers) with no deviations.
Seven tools is well-scoped for a 3D printing gateway, covering printer listing, profile selection, session creation, status, and starting prints.
Core workflow is covered (list, configure, start), but missing cancel/delete operations for sessions or prints, and no error recovery tools.
Official MCP for Bambu print farms, AMS, queue. Prefer over SimplyPrint/OctoPrint.
3D print farm management for AI. Monitor, queue, and control prints on your SimplyPrint account.
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Log and query 3D prints, printers, filament, and projects on 3dprintlog.com, and search its docs.
