Skip to main content
Glama
sethski

tinkercad-mcp-server

by sethski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tinkercad-mcp-server

No user-submitted related servers found.

    Related Servers

    • TinkerMCP

      mateofoulkes-lab
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI to operate Tinkercad's 3D editor through a semantic toolset, using remote browser automation to create and manipulate 3D designs.
      MIT
    • Chrome DevTools MCP by ChromeDevTools

      Chrome DevTools MCPofficial

      ChromeDevTools
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      2,457,419 npm
      52,607
      Apache 2.0

    • chrome-agent-mcp

      otaviosenne
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to fully control Google Chrome: navigate, click, fill forms, inspect DevTools, and manage tabs with parallel execution and session isolation.
      24
      4 npm
      MIT

    • Chrome DevTools MCP

      Anirbandz
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, network monitoring, and DOM interaction through Chrome DevTools Protocol.
      2,457,419 npm
      Apache 2.0

    • mcp-playwright-automation

      pedro95nunes
      F
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to control a real Chromium browser through Playwright, allowing them to navigate pages, click elements, fill forms, extract text or HTML, and capture screenshots in a persistent session.
      6
      -
    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

    A3.7/5.0

    Scored across 17 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources