Serial Hub MCP
Related Servers
Alternatives to Serial Hub MCP
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityCmaintenanceEnables local UART and serial-port debugging through MCP, providing persistent capture, log search, regex/event monitoring, HEX send/query, protocol parsing, and shell-like command sequences.15MIT
- AlicenseNot gradedqualityCmaintenanceLets any MCP-capable AI and a human share a single serial port through one resident daemon, so the AI can read device output, send commands, and drive embedded boards alongside an engineer. It also performs atomic expect→send matching to win sub-second races such as U-Boot countdowns and login prompts, while keeping reads bounded for context hygiene.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables sharing two serial consoles between a local operator and MCP agents, allowing command execution and status monitoring on connected devices.-
- FlicenseNot gradedqualityCmaintenanceLocal MCP server that lets AI agents read and control attached Xshell terminal sessions.10-

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
TDQS
Scored across 8 tools
Each tool maps to a distinct lifecycle stage (list, open, status, read, close) plus a small write family. The send / send_bytes / execute trio is the only fuzzy area, but the descriptions clearly separate text vs base64 vs send-and-observe semantics, so misselection risk is low.
Predominantly verb_noun snake_case (list_ports, open_port, read_output, close_port) with two bare verbs (send, execute) and one noun-first name (port_status). Readable and predictable overall, with only minor deviations in style.
Eight tools is well-scoped for a serial-port bridge: one tool per operation, no redundant wrappers or bloat. Nothing appears vestigial, and no obvious operation is missing a slot.
Full session lifecycle is covered: discovery, open with parameters, state inspection, reads with cursors, multiple write modes, and closing. Gaps are minor but real: no way to reconfigure baud/parity in place (must close and reopen), and no flush/break or DTR/RTS control despite the documented glitch risk.