LightBurn MCP
Related Servers
Alternatives to LightBurn MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to read and create geometry in an open Cadwork 3D document via a local bridge, with queued sequential execution, write approvals, undo support, and a live dashboard for monitoring activity.212AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to discover, connect to, and control LightWave3D Modeler and Layout programmatically via the Command Port.4Apache 2.0
- AlicenseAqualityCmaintenanceLets an AI agent read and edit the Inkscape document you have open in your own window, with millimetre-exact positioning measured on live visual bounding boxes. A revision guard blocks stale edits and every change is verified as landed, all on Inkscape's normal undo stack.24MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and read a self-hosted 3D model library, including G-code revisions, slicer settings, previews, print history and statistics, while also updating tags, descriptions, revision status, logged prints, and imports without delete tools.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to inspect and control running 3ds Max scenes across versions 2016–2025, including object queries, property edits, object creation and deletion, screenshots, file import/export, and MAXScript execution. It also provides API discovery and local documentation search to help verify available classes and properties before scripting.15MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to read, write, and manage Obsidian notes, folders, and periodic notes via the Local REST API, including search and command execution.14MIT
TDQS
Scored across 19 tools
Tools target distinct resource+action pairs: get_cuts vs get_cut (list vs single), get_position vs get_jog_settings vs get_saved_positions, and get_camera_overlay vs its metadata variant are clearly delineated. Minor overlap exists between the state readers (get_position, get_units, get_jog_settings are all subsumed by get_state_snapshot) and among get_status/connection_info/get_state_snapshot, but descriptions disambiguate them.
Strong get_/update_/apply_/upload_/open_ verb_noun pattern throughout, with clean noun suffixes distinguishing variants (_metadata, _snapshot, _settings). The bare 'pair' and noun-phrase 'connection_info' are minor deviations but still readable and unambiguous.
19 tools is slightly above the ideal range but each earns its place in a genuinely layered domain (state reads, cut editing, material library, camera overlay, file import, pairing). No obvious redundant bloat; the granular state getters are defensible as lightweight alternatives to the full snapshot.
Cut handling has read and update but no create/delete or add-layer operation, and there is no jog/move command or job control (start/pause/stop) despite get_jog_settings and job-state reporting — notable gaps for a laser-control surface. The read/derive side and file/camera operations are otherwise well covered.