Skip to main content
Glama
Sign In
qidi-mcp

qidi-mcp

by couplet-physical-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to qidi-mcp

No user-submitted related servers found.

    Related Servers

    • 3d-printagent

      huy97
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage multiple 3D printers via MCP, including monitoring temperatures and progress, uploading and slicing models, controlling prints, and viewing cameras.
      8 npm
      MIT

    • Moonraker MCP

      kascode-com
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to query and control Klipper 3D printers through Moonraker, covering status, temperatures, files, print jobs, and G-code/macro execution, with confirmation gating for dangerous operations.
      MIT

    • printer-mcp

      Synx-x
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an agent to inspect, slice, upload, start, and monitor jobs on a Moonraker/Klipper 3D printer end to end, using one JSON profile for machine-specific configuration. Built-in safety checks block unsafe starts such as incomplete G-code, nozzle mismatches, hot beds, or running jobs.
      MIT

    • prusactl

      trevin-lee
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to monitor and control Prusa 3D printers over PrusaLink or Prusa Connect, including status and camera checks, file upload and print control, G-code execution, queue and history access, and responding to printer dialogs.
      1
      MIT

    • mcp-server-for-bambu

      b84330808
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to monitor and control Bambu Lab 3D printers over a local network via MQTT, including real-time status, AMS filament info, print control, and maintenance tracking. It supports guided setup, safety confirmations, read-only mode, and a built-in printer simulator.
      2
      80 npm
      MIT

    • Creality Print MCP

      mathiasbourgoin
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to prepare and slice models with OrcaSlicer or Creality Print, inspect G-code, and upload, start, pause, resume or cancel jobs on a stock Creality Hi over the LAN. Also exposes status, CFS inventory, camera setup and optional remote-API control of a running Orca slicer GUI.
      MIT
    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

    B3.4/5.0

    Scored across 101 tools

    Disambiguation3/5

    Most tools have a clear distinct purpose, but several clusters overlap heavily: restart_firmware vs restart_klipper_host vs restart_service vs reboot_printer, bed_mesh_calibrate vs qidi_bed_level_calibrate vs z_tilt_adjust, set_temperature vs chamber_heater vs set_polar_cooler, list_fans vs list_devices, run_gcode vs run_macro. The long descriptions do resolve most of these, but the agent must read carefully and an overlap like cooldown/set_temperature(target=0) invites misselection.

    Naming Consistency4/5

    Nearly everything is snake_case with a verb_noun pattern (get_*, set_*, list_*, start_print, cancel_print), which is highly predictable. Deviations are minor: bare noun/verb names (beep, cooldown, chamber_heater, emergency_stop) and domain-prefixed forms (qidi_bed_level_calibrate, bed_mesh_profile, box_*), but the convention stays readable.

    Tool Count1/5

    101 tools for a single 3D printer is an extreme surface; many operations are splintered into near-duplicate tools (four restart variants, three bed-leveling paths, separate list_fans/list_devices/list_directory/list_gcode_files). This far exceeds what an agent can scan and select from reliably, and a large fraction could be consolidated into parameterised tools.

    Completeness5/5

    Coverage of the printer domain is essentially exhaustive: motion, heaters, files/CRUD, job queue, box/multi-filament, calibration, diagnostics, recovery, leases, audit and safety policy all have dedicated tools, with no obvious dead ends. Minor omissions (e.g. no explicit tool-change or PID tuning exposed) are covered by run_gcode/run_macro escape hatches.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources