{"full_name":"DMontgomery40/bambu-printer-mcp","owner":"DMontgomery40","name":"bambu-printer-mcp","shard":"1","url":"https://github.com/DMontgomery40/bambu-printer-mcp","description":"MCP server for Bambu Lab 3D printers — STL manipulation, BambuStudio  or FULU/orca slicing, Blender MCP integration, and direct printer control","homepage":"https://dmontgomery40.github.io/bambu-printer-mcp/","topics":["3d-printing","3js","3mf","bambu-studio","bambulab","blender","blender3d","ftp","mcp","modelcontextprotocol","mqtt","slicer","stl-tools","bambu-cli","bambu-js"],"tag_pages":["3d-printing","blender","ftp","mcp","modelcontextprotocol","mqtt"],"language":"TypeScript","license":"GPL-2.0","avatar":"https://avatars.githubusercontent.com/u/130489651?u=3f5971dbb75903af435b69dfad27de893a0f0fe8&v=4","created_at":"2026-03-16T02:00:33Z","pushed_at":"2026-11-15T11:25:59Z","metrics":{"stars":323,"forks":59,"watchers":3,"issues":21,"prs":144,"releases":88,"issues_open":3,"issues_closed":18,"prs_open":0,"prs_closed":15,"prs_merged":129,"discussions":1},"growth":{"day":{"stars":2,"forks":2,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[300,303,312,313,315,321,323],"forks":[55,56,56,56,56,57,59],"watchers":[null,3,3,3,3,3,3],"issues_open":[null,0,0,0,0,0,3],"prs_open":[null,2,1,0,1,1,0]},"boards":{"weekly_rate":165},"same_owner":[],"issues":[{"number":167,"title":"fusion_mcp_status reports a hung Fusion as responsive: check the write path, not only a read","comments":1,"created_at":"2026-11-15T17:48:42Z"},{"number":165,"title":"Diagnostics redactor: next variants from the final re-check (named entities, 3-tuples, env-name, prefixed multipart, double URL encoding)","comments":0,"created_at":"2026-11-15T08:52:53Z"},{"number":164,"title":"Purpose checks: max penetration depth, mirrored parts, multi-solid parts, and running the purpose tests in CI","comments":0,"created_at":"2026-11-15T08:08:55Z"}],"discussions":[{"number":35,"title":"Printbed clearing","comments":4,"category":"Ideas","created_at":"2026-09-29T13:39:53Z"}],"latest_release":{"name":"v1.1.95 — purpose checks on the design as used, and redacted diagnostics","tag":"v1.1.95","published_at":"2026-11-15T11:23:21Z","body":"\n### Added\n\n- A design's purpose is now data the code engine evaluates (scan-to-make #608). A `cad_run` script declares `PURPOSE` (what it is for, the bought product it follows, what it holds, what carries the load, where its user's eye is) and `use()`, which returns the part as used with `held:<name>` and `world:<name>` bodies. The inspection process compiles the purpose into requirements, adding those its words imply (a holder must name what it holds and mounts to; a vehicle takes 1.5 g jolts; a held screen faces the user), computes the force and moment at each mount from the geometry, and checks tape against 3M VHB's published stresses and that a resting part does not tip, lift or slide. It returns `purpose`, `ready` and `renders.use`. `final: true` is recorded only when the design is ready; otherwise `final_refused` gives the reasons. It fails closed where it cannot compute (tape on a contact that is not one flat patch, a mount declared `other` that carries a held body), still checks tape within a mix of mount kinds, holds the designer's numbers to floors (a held mass that fits the held body's size, at least a 1.5 N press, at most 25° off the user's eye for a screen), and needs each tape or rest surface to be a real slab rather than a block shaped to the part. Mesh mode and 3MF projects are unchanged. Three cookbook examples (`desk_edge_cable_holder`, `desk_clamp_hook`, `phone_stand`) carry a purpose and `use()`.\n- `cad_run` takes `role` (`\"design\"` by default, `\"check\"` for a fit-check part or reference export) and records it on every receipt; a check run is never final and evaluates no purpose. Every valid run that is not final carries `draft_reasons`, plain sentences saying why, for a client that keeps the last valid run as a draft (scan-to-make #790). Receipts without `role` are design runs. Tested with build123d fixtures of the Nov 11 phone holder (a phone square to the cabin on a 30 mm taped strip is refused; the same phone aimed on a 60 mm pad is ready), a stand that tips, a mount not modelled and no purpose, and with a Sonnet-class capability test; nothing was printed or sliced.\n- `counterpart_diagnostics` (counterpart/1) returns this server's own redacted diagnostics bundle for a tester's bug report, `{package, version, files: [{name, content, truncated}], notes}`, so a client's Export Diagnostics can include the MCP's logs without knowing their paths: the configured printer (model, serial, connection route; firmware is not read), its settings, slicer path and version (never by running the slicer), CAD runtime status, recent tool errors, this run's stderr (MQTT and connection messages), redacted as it is captured. The Bambu network plug-in and native helper logs are left out: other programs write them, and they can hold secrets this server cannot recognise. Redaction fails closed: the configured secrets and secret tool arguments go wherever they appear, also URL-encoded, JSON-escaped or base64 (and before a long line is cut); a logged object is redacted by key before it is written, and an object whose field names a secret loses its other values; JSON files are redacted by structure and stay valid; settings show values only for known non-secret settings; and any log line that names a secret, in any spelling or encoding, is withheld whole with the lines that continue it, keeping its time and level. Serial numbers, error codes, firmware versions and whether a secret is set stay. Names, contents and notes never exceed `max_bytes` (default 4 MiB, at most 8 MiB); a missing file is a note. `counterpart_printer_info` advertises it as `capabilities.diagnostics`. Sends nothing to the printer; tested with mocked logs and no printer. `src/counterpart/diagnostics.ts` is shared verbatim with mcp-3D-printer-server. Refs DMontgomery40/scan-to-make#799.\n\n### Fixed\n\n- `cad_run`'s purpose check fails a held body that sits inside the part (more than 1 mm³ and 0.5 mm deep, or more than half of the body) rather than on it, and a part i","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}