Pod

Available as Markdown and JSON. Pod is also available over MCP.

Reported issues for Bambu Printer MCP

Pod holds 6 of 6 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to Bambu Printer MCP.

Most discussed

Identity check rejects an X2D when raw.model_id carries a print-job id ("Printer reported an unknown model identity; cannot verify this printer.")

Tags: [observed 2026-09-29] = seen on 2026-09-29; [source-derived] = read from upstream code; [inference] = my reasoning, please confirm. No credentials, access code or full serial are included.

Summary

On an X2D, the printer status can contain raw.model_id set to a print-job identifier while raw.model is "X2D". observedIdentity() in src/safety/printer-state.ts (added in PR #22, commit f6860e9) treats every declared value as a model identity. model_id here does not normalize…

Read the thread · 2026-09-30 · closed · external user · 2 comments

Printbed clearing

I've been wondering about this for some time and it seems that someone's actually implemented it. This is a feature request based on a demo online: https://x.com/mattshumer_/status/2104777202684301750

Read the thread · 2026-09-29 · closed · external user · 2 comments

H2C Support

Hi, I have a Bambu H2C and want to use this MCP server. The REMOTE-DEPLOYMENT.md mentions H2D/H2S patches but H2C isn't explicitly listed. Are the H2 patches available in the public npm package, or only in a private clone? Will H2C work with BAMBU_MODEL=h2d as a fallback?

Read the thread · 2026-05-24 · closed · external user · 2 comments

A1 detected as A1M from serial prefix (039 / 030 swapped?)

Version: bambu-printer-mcp 1.1.22

My printer is a Bambu Lab A1 (not the mini). Its serial number starts with 039. get_printer_status reports "model": "A1M", also when BAMBU_MODEL=a1 is set.

In dist/printers/bambu.js the serial-prefix detection maps 039 → A1M and 030 → A1. As far as I know, it is the other way round: 039 = A1 and 030 = A1 mini.

The configured BAMBU_MODEL seems to be used for the actual limits, so this looks cosmetic. Maybe the explicit…

Read the thread · 2026-10-02 · closed · external user · 1 comment

profile-flatten.ts resolves inherits but not include, so CLI slicing emits the generic start G-code (A1 and P1S: no AMS selection, no pressure advance, hard-coded nozzle temp)

Summary

src/slicer/profile-flatten.ts walks the inherits chain but never reads the sibling include array. For Bambu's own machine profiles that array is where the real machine G-code lives, so the flattened profile silently falls back to the generic fdm_machine_common start G-code. The slice succeeds, the 3MF looks fine, and the print comes out wrong.

I hit this building my own tooling, made the same mistake, and traced it from a bad physical print back to the profile loader. Your…

Read the thread · 2026-08-31 · closed · external user · 1 comment

H2 series (H2C/H2D/H2S) crashes the MCP server: bambu-node throws "Printer model not supported!"

Running bambu-printer-mcp against a Bambu Lab H2C (LAN Only + Developer Mode, BAMBU_MODEL=h2c). The MCP server process exits roughly 20-30 seconds after every connection.

Stack trace from the Claude Desktop MCP log:

Error: Printer model not supported!
    at TolerantBambuClient.onMessage (bambu-node/dist/index.js:333:16057)
    at MqttClient.listener (bambu-node/dist/index.js:333:12437)
    at MqttClient.emit (node:events:521:24)
Node.js v24.18.0
[bambu-printer] Server…

Read the thread · 2026-07-18 · closed · external user · 1 comment

Most recent

The remaining reports are on the project's issue tracker.