uart-mcp
Related Servers
Alternatives to uart-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceProvides serial debugging for embedded Linux targets, enabling boot log capture, automatic login, crash detection, U-Boot interrupt, and hardware reset via MCP protocol.-

sbl-probeofficial
AlicenseNot gradedqualityDmaintenanceSerial communication and protocol analysis MCP server that gives AI coding assistants direct access to serial ports for reading, writing, decoding, and capturing embedded device output.MIT- AlicenseNot gradedqualityDmaintenanceEnables humans and AI agents to collaboratively control serial ports via MCP tools or Web UI, with real-time data sharing across all participants.MIT
- FlicenseNot gradedqualityBmaintenanceEnables sharing two serial consoles between a local operator and MCP agents, allowing command execution and status monitoring on connected devices.-
- FlicenseNot gradedqualityDmaintenanceEnables reading UART logs from Windows serial ports and sending text to the UART through MCP, with an optional Tkinter UI for local monitoring.1-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with serial devices via MCP tools, providing serial port discovery, connection, read/write, and status management, while sharing the same serial connection with a browser-based terminal.1 npm2Apache 2.0
TDQS
Scored across 15 tools
Each tool has a clearly distinct role—port discovery, capture session management, read variants, write/send/query variants, and offline parsing—so agents can generally select the right tool. The main ambiguity is between serial_write and serial_send, and between serial_read and serial_get_recent, though their descriptions do clarify the intended use cases.
The vast majority of tools follow a serial_<verb> snake_case pattern, which is predictable and easy to scan. However, list_ports and protocol_parse break the serial_ prefix convention, and serial_status and serial_shell are noun-style rather than verb-style, creating minor inconsistencies.
Fifteen tools sits at the upper edge of the well-scoped range and mostly earns its place for a comprehensive UART toolkit. The one-shot variants (serial_send, serial_query, serial_shell) and protocol_parse add specialized capability but make the set feel slightly denser than a minimal capture-focused server.
The tool surface is very complete for UART debugging: it covers port enumeration, capture session lifecycle, continuous reading, writing, event waiting, history search, log paging, buffer reset, and protocol parsing. There are no obvious dead ends or missing core operations for the stated domain.