serial-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_serial_portsA | List available serial ports and USB metadata. |
| serial_force_releaseC | Terminate the process holding a serial port. Destructive. |
| serial_openB | Open a serial session. Close it with serial_close when finished. |
| serial_closeB | Close a serial session and release its port. |
| serial_change_settingsC | Change settings on an open serial session. |
| serial_executeB | Open 8N1, run one text command, and always close. |
| serial_commandC | Send text and collect output until a regex matches, timeout, or silence. |
| serial_wait_forC | Wait for a regex in incoming output, optionally responding on match. |
| serial_writeC | Write text without waiting for a response. |
| serial_readB | Consume buffered text, returning the newest bytes up to the output limit. |
| serial_read_sinceB | Read history without consuming it, returning the newest bytes up to the limit. |
| serial_write_hexC | Write raw bytes supplied as hexadecimal. |
| serial_read_hexC | Consume buffered bytes and return limited hexadecimal output. |
| serial_set_signalsB | Set DTR or RTS on an open session. |
| serial_get_signalsC | Read modem-control signal states. |
| serial_send_breakC | Send a serial break signal. |
| serial_detect_baudC | Try common baud rates and rank readable responses. |
| serial_clear_historyB | Clear a session's receive history. |
| serial_log_startC | Start logging received data to a file. |
| serial_log_stopC | Stop logging and return capture statistics. |
| serial_xmodem_sendC | Send a file with XMODEM checksum or CRC mode. |
| serial_xmodem_receiveB | Receive a file with XMODEM checksum or CRC mode. |
| serial_list_sessionsA | List open serial sessions and cleanup deadlines. |
| serial_statusC | Return connection health and session statistics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| scan_devices | Scan and identify all connected serial devices. |
| detect_baud_rate | Detect the correct baud rate for a serial device. |
| interactive_shell | Open an interactive serial shell session. |
| safe_session | Open a serial session with a reminder to close it when done. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Most tools target clearly distinct operations (read vs read_since vs read_hex are well differentiated by consuming vs non-consuming and text vs binary semantics; write vs write_hex likewise). The boundaries between serial_execute, serial_command, and serial_wait_for are subtler since all send/wait for output, but the descriptions spell out the differences (one-shot close, regex/timeout collection, passive wait-and-respond). Only minor potential confusion remains.
Nearly all tools follow a predictable serial_verb_noun pattern (serial_open, serial_read, serial_write_hex). The one outlier is list_serial_ports, which puts the noun before receiving a serial_ prefix, a small inconsistency. Otherwise the convention is stable and readable.
24 tools is on the heavy side for a serial-port server and pushes into the borderline range. While each tool covers a genuinely different capability (signals, hex I/O, XMODEM, logging, baud detection), the surface feels large enough that some consolidation (e.g. read variants) could have trimmed it.
The surface covers a full lifecycle: open/close/force-release, settings changes, text and hex read/write, signal control, break, baud detection, history, logging, and XMODEM transfer. A minor gap is the absence of a get-settings/read-back tool to complement serial_change_settings, but overall coverage is strong.