Skip to main content
Glama
sabnck

Creality K2 MCP

by sabnck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Creality K2 MCP

No user-submitted related servers found.

    Related Servers

    • bambu-p1s-mcp

      marctheshark3
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to monitor and control a Bambu Lab P1S printer over the local network, including status, file management, slicing, and print operations.
      11
      MIT

    • MCP 3D Printer Server

      DMontgomery40
      A
      license
      B
      quality
      A
      maintenance
      Enables interaction with 3D printer management systems through an MCP server, supporting STL file manipulation, slicing, and control of printers like OctoPrint, Klipper, Duet, and more.
      30
      186 npm
      249
      GPL 2.0

    • print-warden

      moellere
      A
      license
      Not graded
      quality
      C
      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.
      Apache 2.0

    • CAD to Print MCP

      Kayrim
      A
      license
      Not graded
      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.
      MIT

    • bambu-printer

      Ethan2298
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables local Mac agents to monitor and control Bambu Lab 3D printers via MCP tools, including status checks, camera snapshots, and print job management.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.1/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools are clearly separated by domain: status monitoring, job history, file/model/gcode info, slicing, and live printer controls. A couple of pairs such as job_history/recent_logs and printer_status/snapshot could require careful descriptions to avoid misselection, but the names are mostly distinct.

    Naming Consistency5/5

    All tool names use lowercase snake_case and follow a predictable split: noun-style names for queries and data lookups, and verb_noun names for actions like pause_print or set_temperature. This is a consistent and readable convention, even though it is not strictly verb_noun throughout.

    Tool Count5/5

    Fifteen tools is at the high end of the ideal range but is well-justified for a 3D printer MCP covering monitoring, file inspection, slicing, print control, and temperature/fan adjustments. Each tool appears to cover a distinct function without redundant duplication.

    Completeness3/5

    The server covers monitoring, slicing preparation, and print lifecycle controls like pause/resume/cancel, but there is no obvious start_print or execute_slice_plan tool, leaving slice_plan as a dead end for automation. Catalog and model info are present, but upload/delete or direct print-from-catalog workflows are missing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources