arduino-mcp
Related Servers
Alternatives to arduino-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceA local stdio MCP server wrapping arduino-cli to let agents detect boards, manage cores/libraries, compile and upload sketches, and communicate over serial, enabling hardware control without shell gymnastics.17-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Arduino boards for compiling, uploading sketches, and serial communication.6MIT
- AlicenseCqualityDmaintenanceA comprehensive Model Context Protocol (MCP) server for Arduino CLI interactions, built with FastMCP. This server enables AI agents to seamlessly interact with Arduino CLI for development, debugging, code verification, and more.162MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Arduino IDE 2.0 sketches. It exposes a small REST API plus an MCP stdio bridge so agents can read and write the main .ino file, list sources, and optionally compile with arduino-cli.56 npmMIT
- AlicenseAqualityAmaintenanceEnables AI clients to compile and upload Arduino sketches, manage boards, cores, and libraries via arduino-cli, scaffold projects, and read serial output over stdio.26MIT
- FlicenseNot gradedqualityAmaintenanceA fully local MCP server for Mixly that lets AI clients discover boards, scan blocks, build/validate/open projects, generate code, and compile via Arduino CLI—all without uploading source or relying on a remote server.3-
TDQS
Scored across 17 tools
Tools are grouped into clear functional areas (arduino-cli, serial, Ratchet), with distinct purposes. Only board_list and list_ports overlap somewhat, but their descriptions clarify the difference.
Most tools use snake_case with action-first naming (list_ports, serial_open, core_install), but some are noun-first (board_list, core_list, lib_search) creating minor inconsistency. Prefixes also vary by domain, though the pattern is still readable.
17 tools is on the higher end but each serves a distinct purpose across three subdomains (toolchain, serial I/O, Ratchet protocol). The count feels justified for the scope.
Core workflows are covered: toolchain verification, board/core/library management, compile/upload, serial session lifecycle, and Ratchet-specific helpers. Minor gaps like library uninstall or board details exist but are not critical.