SkillAgentSearch skills...

serial-mcp

Serial port MCP server for Claude Code, Codex, Opencode and AI agents. Reliable UART/USB-serial access for embedded development.

Install / Use

claude mcp add qarnet -- npx -y github:qarnet/serial-mcp

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

84/100

Supported Platforms

Claude Code
Claude Desktop
OpenAI Codex

Our assessment of serial-mcp

serial-mcp scores 84/100 on our quality scale, 2853rd of 4,572 Development & Engineering skills we index.

Its MCP Server is 13 KB long, well organised into 21 sections with 7 code examples: a thorough specification that gives an agent plenty to work with.

It has 10 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
4/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 7 days ago, so serial-mcp is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-10-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

serial-mcp compared with similar skills

All 4 of these similar skills score higher than serial-mcp; compare them before choosing.

SkillScoreStarsUpdatedFormat
serial-mcp (this skill)by qarnet84107d agoMCP Server
Agent-Reachby Panniantong10094.3k1d agoCLAUDE.md
headroomby headroomlabs-ai10074.8ktodayCLAUDE.md
CowAgentby zhayujie10047.3ktodayCLAUDE.md
ai-job-searchby MadsLorentzen10045.3ktodayCLAUDE.md

Frequently asked questions

How do I install serial-mcp?
Run claude mcp add qarnet -- npx -y github:qarnet/serial-mcp. The install tabs above show the steps for each supported agent.
Which AI agents does serial-mcp work with?
It is written for Claude Code, Claude Desktop and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
Is serial-mcp safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is serial-mcp still maintained?
The repository was last updated 7 days ago, so serial-mcp is actively maintained.

serial-mcp for UART and USB serial access

GitHub Release crates.io Rust License

serial-mcp is an MCP server for direct access to serial ports. It reads, writes, and streams UART or USB-serial data to microcontrollers, Arduino boards, STM32 chips, and other embedded targets. Reads use timeouts and pattern matching instead of blocking on a serial monitor.

The server provides always-on RX capture. It decodes TX and RX frames using line, delimiter, length-prefixed, start/end, SLIP, and COBS formats. It provides AT, JSON, shell, NMEA-0183, and Modbus ASCII parsers.

Protocol presets provide checksum validation. The server also supports auto-reconnect, event logging, DTR/RTS, BREAK, and flow control. MCP clients can use these features with serial bootloaders, resets, and embedded boards.

Quick start

  1. Install the server. See Install for Cargo, Nix, and prebuilt binary options.
  2. Connect an agent. Follow the agent configuration guide, or use the example below.
  3. Discover devices. Call list_ports() and inspect profile_matches. The result shows what a bare open would reuse.
  4. Open a port. Call open(port=...) with only the port. Baud defaults to 115200/8-N-1. The server reuses the most recently used high-confidence profile for a known device. It creates a durable generated profile for a new device.
  5. Talk to the device. Use transact() for command and response exchanges. Use read() for buffered or unsolicited data. Use write() for send-only operations.

Capabilities

| Area | What it provides | |---|---| | RX model | An always-on ring buffer captures bytes from open to close. read returns buffered bytes immediately. It can also wait, match, and replay history. | | Framing and parsing | Both directions support line, delimiter, length-prefixed, start/end, SLIP, and COBS framing. Parsers include AT, JSON, shell, NMEA-0183, and Modbus ASCII. | | Protocol presets | Seven presets are available. They are at_command, slip, json_lines, cobs, ndjson, nmea0183, and modbus_ascii. Checksum validation is included. | | Device profiles | The server creates automatic profile sessions. High-confidence devices get durable generated profiles. Learned settings persist across sessions. | | Boot capture | capture_boot handles Arduino auto-reset, power-cycle banners, and boot prompts in one atomic call. | | Reliability | Ring wrap is reported through bytes_lost. Encoding fallback is lossless. The server also supports auto-reconnect and reports partial failures. | | Operations | Event logging supports persistent JSONL capture through export_log. The server also provides port allowlisting and stdio and HTTP transports. |

Tool catalog (25 tools)

| Group | Tools | |---|---| | Discovery | list_ports, list_connections | | Connection lifecycle | open, close, reconnect, get_status, reconfigure | | I/O | read, write, transact, capture_boot, flush | | Line control | set_dtr_rts, set_flow_control, send_break | | Profiles & config | list_profiles, open_profile, save_profile, delete_profile, configure, rollback_profile | | Logs & capture | get_log, clear_log, export_log | | Utility | compute_checksum |

Resources and prompts

| Kind | Items | |---|---| | Resources (5) | serial://ports, serial://connections (static); serial://connections/{id}, serial://connections/{id}/raw, serial://connections/{id}/log (templates) | | Prompts (2) | diagnose_port, interactive_terminal |

Install

Cargo (all platforms)

cargo install serial-mcp

Nix

nix profile install github:qarnet/serial-mcp

Prebuilt binary

No toolchain is required. Each release publishes one binary per platform. The latest/download URLs resolve to the newest release.

| Platform | Command | |---|---| | Linux x86_64 | curl -L https://github.com/qarnet/serial-mcp/releases/latest/download/serial-mcp-x86_64-linux -o serial-mcp && sudo install -m 755 serial-mcp /usr/local/bin/ | | Linux ARM64 | Same command with the serial-mcp-aarch64-linux asset | | macOS (Apple Silicon) | Same command with the serial-mcp-aarch64-macos asset | | Windows (x86_64) | Download serial-mcp-x86_64-windows.exe and place it on your PATH |

On Linux, add your user to the dialout group for port access:

sudo usermod -aG dialout $USER

Connect an agent

For client-specific setup, see the agent configuration guide. It covers Claude Code CLI, Claude Desktop, Cursor, VS Code, Zed, opencode, Codex, Hermes, and HTTP transport.

<details> <summary>Quick example (Claude Code, Linux/macOS)</summary>
{
  "mcpServers": {
    "serial": {
      "type": "stdio",
      "command": "serial-mcp",
      "args": ["--allowlist=/dev/ttyACM*,/dev/ttyUSB*"]
    }
  }
}
</details>

Core workflow

Use this sequence for common work: discover, open, talk, verify the learned profile, then use advanced tools when needed.

  1. Call list_ports(). Its profile_matches entries correspond to ports.
    • selected means a bare open reuses selected_profile.
    • ambiguous means equal-ranked profiles require open_profile.
    • duplicate, ineligible, and none mean a bare open starts fresh or transient.
  2. Call bare open(port=...). The result includes the profile binding. The binding reports its name, source, confidence, persistence, generated flag, revision, and dirty state.
  3. Use transact(data=..., match=..., timeout_ms=...) to write and await a response in one call. Use read() for buffered or unsolicited data.
  4. After reconfigure, set_flow_control, or connection-mode configure, inspect profile_persistence. It reports persisted, not_needed, transient, or failed. Also inspect the updated profile binding.
  5. Call close(). A clean close retries a dirty binding as a safety measure.

For boot and reset capture, call capture_boot. It handles Arduino auto-reset, power-cycle banners, and boot prompts.

The call purges unread OS input. It marks the RX live edge. It can pulse DTR/RTS, with guaranteed release. It captures only post-mark bytes on a private cursor. The result is bounded in memory and does not write a file. See RX and reading for the from cursor model. See Device profiles for profile behavior.

Protocols

The protocol field supplies framing and parser defaults for both directions. NMEA and Modbus ASCII presets validate checksums:

| Preset | Wire name | Framing / parser | |---|---|---| | AT commands | at_command | Line (CR) + AT parser | | SLIP | slip | RFC 1055 byte stuffing | | JSON lines | json_lines | Line + JSON-lines parser | | COBS | cobs | Consistent Overhead Byte Stuffing | | NDJSON | ndjson | Line + JSON-lines parser, skips blank lines | | NMEA-0183 | nmea0183 | Start/end $/! + NMEA parser, *XX checksum | | Modbus ASCII | modbus_ascii | Start/end : + Modbus ASCII parser, LRC |

Field precedence is explicit call field, call-time preset, connection default, then connection preset. The Protocol guide documents this order, checksum behavior, and the framing and parser reference.

Key concepts and guides

| Guide | What it covers | |---|---| | RX and reading | Ring buffer and shared cursor. Tagged from forms. Timeouts, silence, and matching. Ring wrap and bytes_lost. Encoding fallback, flow control, capture_boot, and subscriptions. | | Device profiles | profile_matches outcomes and identity rules. Generated and reused selection. Learning, revision CAS, rollback, and deletion guards. | | Persistent capture | The export_log contract. Quotas, portable filenames, atomicity, and failure semantics. | | Agent configuration | Client setup. HTTP transport. Troubleshooting. | | Protocol guide | Framing and parsers. Presets and precedence. Checksum behavior. | | Documentation index | User and development guides |

Transports and options

| Mode | How to activate | Use case | |---|---|---| | stdio | default | Desktop agents | | HTTP | --transport=http | Remote and headless use |

<details> <summary>CLI options</summary>
serial-mcp [OPTIONS]

  --transport <stdio|http>          Transport to use (default: stdio)
  --allowlist <patterns>            Comma-separated glob patterns for allowed ports
  --bind <addr>                     HTTP bind address (default: 127.0.0.1:8000)
  --max-program-buffered-bytes <N>  Global budget for all in-flight RX tools
  --max-tool-buffered-bytes <N>     Per-tool ceiling for max_buffered_bytes
  --profiles-path <path>            Profile store file path (default: OS user config dir + serial-mcp/profiles.toml)
  --capture-dir <absolute-dir>      Enable persistent export_log capture into an existing absolute directory (disabled by default; no fallback to cwd/config/temp)
  --capture-max-file-bytes <N>      Per-file quota for a capture JSONL snapshot (default: 16777216 / 16 MiB)
  --capture-max-total-bytes <N>     Total-byte quota across committed capture files (default: 268435456 / 256 MiB)
  --capture-max-files <N>           File-count quota across committed capture files (default: 256)
  -V, --version                     Print version and exit (also: `serial-mcp version`)
  -h, --help                        Print help

  RUST_LOG                   Log level env var (error/warn/info/debug/trace)
</details>

The profile store is one TOML file shared by every session. Use --profiles-path for an isolated store. See Device profiles.

Persistent capture

export_log writes portable .jsonl filenames into the --capture-dir root. It never accepts arbitrary paths and never overwrites files. See Persistent capture.

MCP compatibility

serial-mcp supports MCP 2025-11-25. This version uses the legacy session lifecycle.

It also supports MCP 2026-07-28. This version uses modern discovery and stateless requests with SEP-2549 cache fields. Both stdio and HTTP transports support the port allowlist.

CI runs official conformance checks and Inspector interoperability checks. The validation tools come from the committed npm lockfile. CI installs them with npm ci --ignore-scripts. It runs them as local binaries, never through npx.

An actual historical rmcp 1.7.0 client tests backward compatibility over HTTP and stdio. Run the complete local and CI version gate with:

bash scripts/test-mcp-compat.sh

Development

Before pushing or opening a pull request, run cargo fmt --all. CI runs cargo fmt --all -- --check once in standalone Ubuntu format job first. Formatting failures block dependent expensive Nix, build/test/Clippy, and MCP conformance jobs.

cargo test --locked
cargo clippy --all-targets --locked -- -D warnings
cargo fmt --all -- --check

# Linux-only required Rust PTY fixture suites
cargo test --locked --test device_fixture -- --test-threads=1
cargo test --locked --test device_command_parity -- --test-threads=1
cargo test --locked --test device_framing_parity -- --test-threads=1
cargo test --locked --test device_protocol_parity -- --test-threads=1
cargo test --locked --test device_

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars10
CategoryDevelopment
Updated7d ago
Forks1

Languages

Rust

Trust signals

97/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info