tinkercad-mcp-server
Related Servers
Alternatives to tinkercad-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI to operate Tinkercad's 3D editor through a semantic toolset, using remote browser automation to create and manipulate 3D designs.MIT
- AlicenseAqualityDmaintenanceEnables LLMs to interact with MIT App Inventor, AndroidBuilder, Kodular, or Niotron IDEs in real-time, controlling the Designer and Blocks workspace via Chrome DevTools Protocol.10MIT
- AlicenseAqualityBmaintenanceEnables AI agents to observe and control a browser-based 2D robot simulator, including driving, configuring sensors and modules, running programs, and generating wiring, firmware, and parts lists for ESP32, Arduino Uno, or Raspberry Pi.410MIT
- AlicenseBqualityBmaintenanceEnables an agent to drive the Bambu Lab CyberBrick desktop app over the Chrome DevTools Protocol, covering the whole device setup workflow — planning hardware connections, authoring and reading firmware configuration, managing projects, and flashing firmware, MPY and config files to boards.4194 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools. Provides browser automation, performance analysis, debugging capabilities, and network request monitoring.1,865,622 npm54,821Apache 2.0
- AlicenseBqualityDmaintenanceEnables AI agents to fully control Google Chrome: navigate, click, fill forms, inspect DevTools, and manage tabs with parallel execution and session isolation.246 npmMIT
TDQS
Scored across 17 tools
Each tool targets a clear editor action, and the descriptions make the intended usage explicit. Minor ambiguity exists between tinkercad_get_circuit (which can include code) and tinkercad_get_code, and between tinkercad_build_circuit and the primitive tools it wraps, but the documentation explains these relationships.
All tools share the tinkercad_ prefix and almost all use snake_case verb_noun names like open_circuit, add_component, and delete_wire. A couple of names deviate from the strict verb_noun pattern, such as tinkercad_login_status and tinkercad_screenshot, so the consistency is strong but not perfect.
With 17 tools, the set is slightly above the ideal 3-15 range, but every tool maps to a meaningful step in the Cireuits workflow: opening, inspecting, placing, wiring, coding, simulating, and observing. The convenience build_circuit tool adds some redundancy, but it is justified as a higher-level workflow over the primitives.
The tool surface covers the main build/edire/simulate lifecycle well: open, read, add, move, delete, wire, set attributes, write code, run simulation, read serial, and capture screenshots. Notable non-critical gaps include serial input, explicit save/export, undo/redo, and project-level operations like deleting or renaming circuits.