Skip to main content
Glama
SlicerBridge

SlicerBridge

SlicerBridge

A Rosetta Stone for multicolor 3MF files. Any multicolor project in, a ready, checked file for every multicolor printer out.

CI License: GPL v3 Python 3.10+

You paint a multicolor model in one slicer. The people who print it own a Bambu Lab A1, a Creality K2, an Elegoo Centauri Carbon, a QIDI Q2, a Prusa XL, a Snapmaker U1… and each of them has to retarget your project to their printer by hand, guessing at presets, and often losing the colors on the way.

Every slicer and printer speaks its own dialect of the same 3MF format. SlicerBridge is the translator: it reads your project once and writes it out in each printer's dialect without losing its meaning: the colors, the size, and the way you set it up to print.

SlicerBridge takes the project from whichever slicer you made it in (Bambu Studio, OrcaSlicer, or a printer maker's own fork of either) and writes one file for each of 35 printers, named for that printer (My Model - Creality K2 Plus.3mf), so a downloader can open theirs and print. Its files for Bambu Lab, OrcaSlicer-family and U1 printers can go back in, for yet another printer. Every file:

  • keeps the colors where you painted them. The filaments a model actually uses are kept in order, and every painted triangle is re-encoded to match.

  • carries that printer's own settings, written by its own slicer, and that printer's filament presets. Your print settings (layer height, walls, infill, supports, brim, ironing and the rest that shape the print) come along where the printer has the same setting, whether or not your project marks them as changed. A value the printer's slicer won't take keeps the printer's own, and the output says so.

  • gets a prime tower built for its height. A print taller than 100 mm gets a heavier tower (a wider brim, longer and wider ribs, wider purge spacing, a slower tower), so a tall, thin tower doesn't get knocked over partway up. Each file gets the heaviest one its bed has room for, and the output says which.

  • keeps its size. Nothing is ever scaled. A model bigger than a bed gets a warning with the scale that fits.

  • is checked before it's written: colors, paint, plates, size, settings and the tall-print tower. With --slice it's also sliced in that printer's slicer (Snapmaker Orca for the U1), proving automatic color changes and a prime tower clear of the model, and reporting the print time, the grams and the prime tower's share of the filament. A file that fails a check is never written.

What goes in

A multicolor .3mf project, painted or with colors per part or object, saved by any of these. They all write the same project format.

Saved by

Bambu Studio

tested (2.8)

OrcaSlicer

tested (2.4.2)

QIDI Studio, Anycubic Slicer Next, ElegooSlicer, Flash Studio

tested with projects each of them saved

SlicerBridge

its files for Bambu Lab, OrcaSlicer-family and U1 printers, to retarget them again

Creality Print

should work, not yet tested: its command line can't save a project (tell us)

PrusaSlicer

not yet: PrusaSlicer projects are a different format

A mesh-only 3MF (no slicer project inside) is refused with what to do: open it in your slicer, give it its colors, and save the project.

Related MCP server: ps3d

What comes out

Printer

Key

Colors

File built for

Brand slicer checked

Bambu Lab A1 mini

a1mini

4

Bambu Studio

—

Bambu Lab A1

a1

4

Bambu Studio

—

Bambu Lab P1S

p1s

16

Bambu Studio

—

Bambu Lab P2S

p2s

16

Bambu Studio

—

Bambu Lab X1 Carbon

x1c

16

Bambu Studio

—

Bambu Lab H2S

h2s

16

Bambu Studio

—

Bambu Lab H2D

h2d

16

Bambu Studio

—

Bambu Lab H2D Pro

h2dpro

16

Bambu Studio

—

Bambu Lab H2C

h2c

16

Bambu Studio

—

Bambu Lab X2D

x2d

16

Bambu Studio

—

Bambu Lab H3C

h3c

9

Bambu Studio

—

Creality K2 Plus

k2plus

4

OrcaSlicer

Creality Print

Creality K2 Pro

k2pro

4

OrcaSlicer

Creality Print

Creality K2 SE

k2se

4

OrcaSlicer

Creality Print

Creality Hi

hi

4

OrcaSlicer

Creality Print

Creality K1C CFS

k1c

4

OrcaSlicer

Creality Print

Elegoo Centauri Carbon

cc

4

OrcaSlicer

ElegooSlicer

Anycubic Kobra S1

kobras1

4

OrcaSlicer

Anycubic Slicer Next

Anycubic Kobra S1 Max

kobras1max

4

OrcaSlicer

Anycubic Slicer Next

Anycubic Kobra 3

kobra3

4

OrcaSlicer

Anycubic Slicer Next

Anycubic Kobra 3 Max

kobra3max

4

OrcaSlicer

Anycubic Slicer Next

Anycubic Kobra X

kobrax

4

OrcaSlicer

Anycubic Slicer Next

Flashforge AD5X

ad5x

4

OrcaSlicer

Flash Studio

Flashforge Creator 5

creator5

4

OrcaSlicer

Flash Studio

Flashforge Creator 5 Pro

creator5pro

4

OrcaSlicer

Flash Studio

QIDI Q2

q2

4

OrcaSlicer

QIDI Studio

QIDI Q2C

q2c

4

OrcaSlicer

QIDI Studio

QIDI Plus4

plus4

4

OrcaSlicer

QIDI Studio

QIDI Max4

max4

4

OrcaSlicer

QIDI Studio

WonderMaker ZR Ultra S

zrultras

4

OrcaSlicer

—

Prusa MMU3

mmu3

5

PrusaSlicer

—

Prusa XL

xl

5

PrusaSlicer

—

Prusa Core One INDX 4T

indx4

4

PrusaSlicer

—

Prusa Core One INDX 8T

indx8

8

PrusaSlicer

—

Snapmaker U1

u1

4

Snapmaker Orca

—

"File built for" is the slicer whose settings the file carries. Files for Creality, Elegoo, Anycubic, Flashforge and QIDI printers are written by OrcaSlicer and also checked in each maker's own slicer: see docs/brand-slicers.md for what those slicers read differently, and how the files handle it.

Each filament gets the printer's own preset for its type, never another type's: PLA, PETG, PCTG, ABS, ASA, PC, nylon (PA), the carbon-fibre PLA-CF, PETG-CF and PA-CF, HIPS, PVA, BVOH and TPU, wherever the printer's slicer has a preset for it. Every Bambu printer has them all but the A1 mini, which has no ABS, ASA, PC or nylon; the U1 has them all but HIPS. A type a printer has no preset for is refused, with which filament and why. Each Prusa tool gets Prusa's own preset for its type (Prusament, Prusa ABS), or else PrusaSlicer's Generic one: the XL takes PLA, PETG, ABS, ASA, PC, PETG-CF, PA-CF, HIPS and TPU; the Core One INDX PLA, PETG, ABS, ASA, PC, PETG-CF, PVA and TPU; the MMU3 PLA, PETG, ABS, ASA and PC.

Bambu's two TPUs stay apart. Plain TPU (soft, 95A and the like) gets each Bambu printer's Generic TPU, and the output says to load it by hand on the external spool, since an AMS can't feed it; on the H2D, H2D Pro, H2C and X2D it goes on the one nozzle its preset allows. Bambu's TPU for AMS gets Generic TPU for AMS. Every OrcaSlicer-family printer gets its maker's own TPU preset, except the Flashforge Creator 5 and 5 Pro, whose TPU presets OrcaSlicer types otherwise; none of them takes TPU for AMS. The U1 prints TPU on Generic TPU, and TPU for AMS on Snapmaker's TPU 95A HF.

Some slicers won't print two filaments together until a preference allows it, and the output says which: OrcaSlicer, a PLA and PETG model on a printer whose colors share one nozzle (a K2 Plus, say); Snapmaker Orca, PLA with ABS, ASA, PC or nylon on the U1. PrusaSlicer prints any of them together, without a warning; the output says when the MMU3's filaments print at different temperatures through its one nozzle (PrusaSlicer sets each one's at its change, and doesn't wait for it), and when a Prusa printer's filaments want bed temperatures more than 15 C apart (PrusaSlicer heats the one bed for the first filament each layer prints).

Missing your printer? Ask for it, or add it.

Install

SlicerBridge runs on macOS and Windows (what's different there; Linux: help wanted), with Python 3.10 or newer.

pipx install slicerbridge                                    # or: uv tool install slicerbridge
pipx install git+https://github.com/UnicornGraveyard/SlicerBridge   # the latest from GitHub

It builds each printer's settings with that printer's slicer, so install the ones you need:

To write files for

Install

Bambu Lab printers

Bambu Studio

Creality, Elegoo, Anycubic, Flashforge, QIDI, WonderMaker

OrcaSlicer 2.4.2

Prusa printers

PrusaSlicer

Snapmaker U1

nothing: its templates are built in (Snapmaker Orca to --slice it)

Then slicerbridge doctor shows what it found. Details, other install locations and environment variables: docs/install.md.

Use

slicerbridge inspect model.3mf                       # colors used, plates, fit on each bed
slicerbridge convert model.3mf                       # the popular printers, into out/<model>/
slicerbridge convert "Dragon - Creality K2 Plus.3mf" --printers bambu   # retarget a file you already have
slicerbridge convert model.3mf --printers all --slice --name "My Model" --prefix "My Shop - "
slicerbridge convert model.3mf --name "My Model" --suffix "My Shop"   # My Model - Prusa XL - My Shop.3mf
slicerbridge convert model.3mf --printers creality,qidi,u1
slicerbridge printers                                # every printer: its key, engine, slicer, filament types
slicerbridge verify "out/My Model" --source model.3mf --slice
slicerbridge brand-check "out/My Model"              # slice each file in its maker's own slicer

--printers takes all, popular, a vendor (bambu, creality, elegoo, anycubic, flashforge, qidi, wondermaker, prusa, snapmaker), or printer keys, comma-separated.

What it won't do

  • Merge colors. A model that uses more filaments than a printer holds is refused for that printer. Which two colors to merge is a design decision; make it in your slicer. (Prusa printers take an explicit --map.)

  • Resize anything. Size is never a reason to skip a printer either: the downloader scales it in their slicer.

  • Write a file that failed a check, or overwrite a file it didn't write (those move to _previous/).

Use it from Claude or another AI assistant

SlicerBridge includes a local MCP server, so an assistant can inspect a model, convert it for the printers you name, and read the check results for you. It runs on your machine over stdio, with your slicers: nothing is uploaded.

Claude Code and Cowork: install the SlicerBridge plugin, which adds the server and a skill that teaches Claude the workflow. It needs uv.

/plugin marketplace add UnicornGraveyard/SlicerBridge
/plugin install slicerbridge@slicerbridge

Any other MCP client: run uvx slicerbridge mcp (or slicerbridge mcp once installed). Setup for Claude Desktop and others: docs/mcp.md. It's also listed in the MCP Registry as io.github.UnicornGraveyard/slicerbridge.

How it works

Every input is read the same way: Bambu Studio, OrcaSlicer and their forks save the same 3MF project format (meshes, paint, plates, settings). Three engines write the outputs, sharing one printer table, one CLI and one set of checks:

  • orca: Bambu Lab and OrcaSlicer-family printers. Each printer's slicer writes its settings once, from its own bundled presets (templates). A file is the source project with those settings, its filaments compacted and its paint re-encoded, each plate moved onto its own plate of the new bed with room for the prime tower.

  • prusa: Prusa multi-material printers, written by Panda2Prusa as PrusaSlicer projects, one per plate.

  • u1: the Snapmaker U1, with bl2u1's U1 templates. With --slice, Snapmaker Orca slices the file.

docs/how-it-works.md explains each step; docs/checks.md lists every check.

Contributing

Bug reports, printer requests and pull requests are welcome: start with CONTRIBUTING.md. Please don't attach paid or licensed models to issues; the test suite builds its own projects.

License and credits

SlicerBridge is free software under the GNU GPL v3 or later. It stands on Panda2Prusa (MIT, vendored) and bl2u1 (GPLv3, its U1 templates), and on the work of the OrcaSlicer, Bambu Studio and PrusaSlicer projects, whose profiles it reads from your own installs. See THIRD_PARTY_NOTICES.md.

Made by Unicorn Graveyard, who needed every ColorStacked model to reach every printer.

Available Tools

6 tools
brand_checkA
Read-onlyIdempotent

Slice each file in the slicer its printer's maker ships (Creality Print, ElegooSlicer, Anycubic Slicer Next, Flash Studio, QIDI Studio), where installed, and report what that slicer makes of it.

Inputs: paths (required), printers. Returns: result

convert_modelA
Idempotent

Write a ready file per printer for a multicolor .3mf project (from Bambu Studio, OrcaSlicer, a maker's fork, or a file SlicerBridge wrote), each one checked before it is kept. Files go in <out_dir>//, named ' - .3mf', or ' - - .3mf' with a suffix. A printer the model can't go to (more colors than it holds, an unknown filament type) is refused with the reason; nothing wrong is written.

Inputs: model_path (required), name, prefix, suffix, +3 more. Returns: result

doctorB
Read-onlyIdempotent

Which slicers SlicerBridge finds, their versions, and where it keeps its templates.

Inputs: no named parameters. Returns: result

inspect_modelA
Read-onlyIdempotent

Describe a multicolor .3mf project: its palette, the filament slots it actually uses, each plate's size, and whether it fits each printer's bed (and at what scale if not).

Inputs: model_path (required), printers. Returns: result

list_printersB
Read-onlyIdempotent

Every printer SlicerBridge writes for: its key, name, engine, slicer, the colors it holds, the filament types it takes (any other is refused), and the sets it's in.

Inputs: printers. Returns: result

verify_filesA
Read-onlyIdempotent

Re-run SlicerBridge's checks on files it wrote (colors, paint, plates, size, settings), and optionally slice each one.

Inputs: paths (required), slice_files, source_path. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools target a clearly distinct phase of the workflow: list_printers (discovery), inspect_model (input analysis), convert_model (output writing), doctor (environment diagnostics). brand_check and verify_files both revolve around checking/slicing files, which could cause occasional misselection, though the descriptions distinguish third-party slicer comparison from re-validating SlicerBridge's own output.

    Naming Consistency4/5

    Five of six tools follow a clean verb_noun snake_case pattern (brand_check, verify_files, list_printers, convert_model, inspect_model). 'doctor' is a bare noun diagnostic command, a minor deviation from the otherwise consistent convention.

    Tool Count5/5

    Six tools is well-scoped for a slicer bridge: discovery, inspection, conversion, verification, brand comparison, and diagnostics each earn a distinct place. Nothing feels padded or missing at this count.

    Completeness4/5

    The core lifecycle is covered: list printers, inspect a model, convert it, then verify the written files, with doctor and brand_check as supporting operations. Minor gaps exist around managing/registering printers or templates and cleaning up old outputs, but agents can work around these for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to work with OrcaSlicer code and perform slicing operations, such as reading files, checking Git status, and slicing 3D models to get print time and filament usage.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI hosts to interact with a browser CAD workbench through model-neutral local stdio or authenticated remote MCP tools, supporting command discovery, design-health analysis, and scoped previews while never reading local files or taking over open sessions.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to prepare and inspect STL/3MF files and run offline slicing on an isolated Windows desktop while leaving the mouse, keyboard, and visible desktop usable; also supports an X2D dual-nozzle workflow with offline validation of sliced 3MF archives and nozzle assignments.
      GPL 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLM clients to slice, paint, and verify 3D prints through the installed slicer's command line for any installed Bambu printer, nozzle, and filament, with settings per object type. It never sends jobs to a printer.
      11
      MIT