MCP.Market

Serial Console MCP: AI for telecom equipment and any serial device MCP server

by sbrunner-atx·io.github.sbrunner-atx/serial-console-mcp·v0.3.2·1 stars

Let AI configure telecom gear over serial: Juniper and Cisco, Icom CI-V, Yaesu/Kenwood CAT, rotators

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

1 stars29 downloads/wk

Reviews

Write one

Nobody has reviewed Serial Console MCP: AI for telecom equipment and any serial device yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Serial Console MCP: AI for telecom equipment and any serial device tools (30, 5 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • capture_start

    Start writing this connection's traffic to a file until capture_stop.

  • capture_stop

    Stop the capture started by capture_start and report the file and size.

  • cat_build

    Build a ';'-terminated text CAT command (Kenwood, Elecraft, Yaesu) for query_text or send_text with line_ending="NONE".

  • cat_parse

    Decode ';'-terminated text CAT replies: rig id to model, FA/FB to MHz, MD to mode name, IF to frequency/mode/VFO/split/TX state, and the ?; E; O; error answers. Pass the text returned by query_text.

  • civ_build

    Build an Icom CI-V frame as hex, ready for send_hex.

  • civ_freq

    Convert between a frequency in MHz and CI-V BCD data bytes.

  • civ_parse

    Decode Icom CI-V frames from hex (as returned by read_available).

  • clear_buffer

    Discard any buffered received data. Handy right before sending a command so the next read starts clean (drops old echo, prior output, or syslog noise).

  • connect
  • detect_baud

    Try common baud rates on a closed port and rank them by how readable the reply is. Use when the user doesn't know the device's rate.

  • disconnect

    Close a serial port and free it for other programs.

  • expectwrite action

    Run a scripted sequence of send-and-wait steps in one call, like `expect`.

  • get_transcript

    Return the tail of everything received on a connection since it was opened.

  • list_presets

    Show the device presets `connect(preset=...)` understands, with their settings.

  • list_serial_ports

    List every serial port the computer can currently see.

  • port_in_use_by

    Report which program currently holds a serial port (macOS/Linux, via lsof).

  • pulse_line

    Drive DTR or RTS to `level` for `ms` milliseconds, then restore it.

  • query_text

    Convenience: clear the buffer, send an ASCII command, and read the reply.

  • read_available

    Drain and return whatever the device has sent, without transmitting anything.

  • read_until_prompt

    Read accumulated output until a prompt appears, or until timeout.

  • reconnect_last

    Reconnect to a remembered port with the same settings as last time.

  • rotator_build

    Build a Yaesu GS-232A/B rotator command for send_text (CR) or query_text.

  • rotator_parse

    Decode a GS-232 reply into azimuth/elevation degrees ("+0180", "+0180+0045", "AZ=180 EL=045") or the ?> rejection.

  • screen

    Show the current terminal screen of a vt100/xterm connection: what a person at a real terminal would see right now, as rows of text, plus the cursor position. This is how to read full-screen interfaces (BIOS setup, RAID/BMC consoles, menu-driven switches, vi, top): press keys with send_keys, then look at the screen again.

  • send_breakwrite action

    Send a BREAK condition (TX held low) for `ms` milliseconds.

  • send_hexwrite action

    Send raw bytes given as hex. Writes to TX only; does NOT read.

  • send_keyswrite action

    Press keys by name, encoded the way a VT100/xterm terminal sends them.

  • send_textwrite action

    Send an ASCII command to the device. Writes to TX only; does NOT read.

  • set_lines

    Set the DTR and/or RTS output lines and hold them.

  • status

    Report every open port: settings, reader state, buffered bytes, control-line states, capture, and which connection is current. With nothing open, lists what reconnect_last remembers.

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan14 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Serial Console MCP: AI for telecom equipment and any serial device compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 1,119 Developer tools servers
Tools
30
the typical Developer tools server has 7
Tools that change things
17%
typical: 5%. Fewer write tools means less an agent can break
GitHub stars
1
more than 50% of 855 Developer tools servers
Downloads a week
29
more than 13% of 436 Developer tools servers with a package

What its tools let an agent do: 24 read · 2 change · 4 send or post

Install Serial Console MCP: AI for telecom equipment and any serial device in Claude Code, Cursor or VS Code

claude mcp add serial-console-mcp -- uvx serial-console-mcp
Add to Cursor

What the publisher says

From the Serial Console MCP: AI for telecom equipment and any serial device repository's README, as published. We do not edit it. Read it on GitHub

serial-console-mcp

<!-- mcp-name: io.github.sbrunner-atx/serial-console-mcp -->

AI for the configuration of telecommunication equipment, through the console port it already has.

&nbsp;MIT licensed &nbsp;·&nbsp; Python 3.10+ &nbsp;·&nbsp; status: 0.3.2, verified live on a Juniper EX2200 console

serial-console-mcp connects an AI assistant such as Claude to the serial console of the equipment that runs networks and radio stations, and of anything else with a serial port:

craft ports: log in, read state, change configuration with a safety net (commit confirmed on Junos, reload in on IOS), and leave the console as it was found.

  • Routers and switches. Juniper (Junos) and Cisco (IOS, IOS-XE) console and

over their text CAT protocols: identify the rig, read and set frequency and mode.

  • Radio transceivers. Icom and Xiegu over CI-V; Kenwood, Yaesu and Elecraft

read the heading, turn, stop.

  • Antenna rotators. Yaesu GS-232 and the many controllers that speak it:

talks raw bytes, cleans up ANSI output, or keeps a full VT100/xterm screen, so IoT gateways, alarm and access-control panels, UPS and PDU menus, lab instruments, industrial controllers, Linux and BIOS consoles and microcontrollers work too.

  • Anything else with a serial port. Nothing is tied to telecom: the server

You say what you want in plain language. The assistant drives the console through this server, Claude Desktop asks you to approve each step, and bundled operating skills teach it the Junos and IOS basics: which mode a prompt means, how to get in and out, which show commands answer everyday questions.

Juniper support is verified on a real EX2200 console. Cisco, CI-V, CAT and rotator support follows the vendors' protocol references and has not yet met hardware on this bench. The other device types use the generic tools rather than device-specific helpers.

You do not need to know any programming. After it's installed you talk to Claude normally:

You: What serial ports do you see?

Claude: I found two. One looks like a Silicon Labs CP210x on COM4 — that's

probably your device.

You: Connect to COM4 at 9600 baud.

Claude: Connected.

You: Log in and show me the version.

How it works (the important part)

A serial console isn't a simple question-and-answer channel. It echoes what you type, prints unsolicited messages on its own (logs, interface flaps), and can dump pages of output. So the moment a port is open, a background reader keeps draining it into a buffer. That means Claude can:

reply — even a long one — without cutting it off, or

  • send a command (writes only — doesn't guess when the reply is done), then
  • read until a prompt appears (# , > , login: …) to capture the whole
  • read whatever's waiting for streaming/unsolicited output.

This is the same model minicom and expect use, which is why it handles interactive CLIs properly.

The tools

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Serial Console MCP: AI for telecom equipment and any serial device: common questions

Is Serial Console MCP: AI for telecom equipment and any serial device MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Serial Console MCP: AI for telecom equipment and any serial device safety report
How do I install Serial Console MCP: AI for telecom equipment and any serial device?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Serial Console MCP: AI for telecom equipment and any serial device need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Serial Console MCP: AI for telecom equipment and any serial device maintained?
The last commit was 36 days ago (2026-09-29). The latest release is v0.3.2.
What can I use instead of Serial Console MCP: AI for telecom equipment and any serial device?
Servers from other publishers that do the same job: Skills Anywhere MCP server, Yaver MCP server and Suvadu MCP server.
How does Serial Console MCP: AI for telecom equipment and any serial device compare with other Developer tools MCP servers?
safety score 92/100 (higher than 90% of 1,119 Developer tools servers); tools 30 (the typical Developer tools server has 7); tools that change things 17% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Serial Console MCP: AI for telecom equipment and any serial device

Same job from other publishers: the closest match first, then the best rated.

  • Skills Anywhere
    Discover and load Agent Skills from configured local directories and Git sources over stdio MCP.
    A
  • Yaver
    Phone-first OpenCode MCP for trusted devices: run, build, deploy, and manage endpoint-local tools.
    C
  • Suvadu
    Local shell history and AI agent sessions over MCP: search commands, failures, risk and git changes
    A
  • Akb
    Git-backed org memory for AI agents — hybrid search, tables, files & a URI graph over MCP.
    A

More from sbrunner-atx →