Skip to main content
Glama
RRS OrcaSlicer MCP

RRS OrcaSlicer MCP

Related Servers

Alternatives to RRS OrcaSlicer MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to slice STL/3MF models through an official, unmodified slicer CLI, list machine/process/filament profiles, apply setting overrides, and inspect G-code statistics.
      10
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      MCP server for BambuStudio slicer: inspect geometry, configure saved projects, and compare slices with Claude Code or Codex.
      29
      2
      AGPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to inspect FreeCAD documents and export named solids to STL, find and derive OrcaSlicer presets, preview and run slices with recorded manifests, and then read G-code metadata, query a Moonraker printer, upload G-code, and start an uploaded print as a separate confirmed step.
      15
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes MCP tools that slice models with headless OrcaSlicer, stage gcode on Moonraker-based Klipper printers, gate job starts behind explicit operator authorization, and report status, telemetry-derived events, snapshots, and alerts. It also manages spools and lets AI agents query job estimates, blockers, and start-precondition checks.
      1
      Apache 2.0
    • A
      license
      C
      quality
      B
      maintenance
      Enables AI assistants to drive PrusaSlicer through MCP: select profiles, manage bed models, slice with verified settings, analyze G-code and print risks, and upload or control prints on networked printers.
      33
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for pre-print QA of Bambu Studio projects, providing tools to inspect models and 3MF files, validate risky settings, create support variants, and open files in Bambu Studio.
      MIT

    TDQS

    C2.9/5.0

    Scored across 63 tools

    Disambiguation2/5

    The set contains many similarly purposed tools across domains: host_request_status, native_request_status, printer_request_status, job_status, and batch_status all retrieve status/receipts, while host_model_read, host_model_detail, project_inspect, project_objects_read, and project_geometry_read overlap in reading model/project structure. Descriptions add context, but at 63 tools an agent can easily misselect between host, native, project-file, and desktop paths.

    Naming Consistency4/5

    All names use snake_case and consistent domain prefixes such as host_, native_, printer_, settings_, project_, batch_, and job_. There are minor inconsistencies in action placement and plurality, e.g. job_status vs jobs_list, host_presets_list vs host_preset_read, and noun_verb vs verb_noun forms, but the pattern remains readable.

    Tool Count1/5

    The server exposes 63 tools, far beyond a well-scoped MCP surface. Although the OrcaSlicer domain is broad, the count includes many specialized variants, status/request tools, and overlapping read/write paths that make the set overwhelming rather than proportionate.

    Completeness4/5

    Coverage is broad across slicing, host bridge, native GUI operations, printer control, settings/profiles, project/mesh editing, jobs, and desktop automation. Remaining gaps include missing delete/rename operations for profiles or workspace artifacts and limited printer file management, which are mostly workaroundable.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data