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

Name: Serial Console MCP: AI for telecom equipment and any serial device
Author: sbrunner-atx

作者：sbrunner-atx版本 0.3.2i★ –i在你的电脑上运行

注册名称io.github.sbrunner-atx/serial-console-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 46/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "serial-console": {
      "command": "uvx",
      "args": [
        "serial-console-mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add serial-console -- uvx serial-console-mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "serial-console": {
      "command": "uvx",
      "args": [
        "serial-console-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "serial-console": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "serial-console-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 sbrunner-atx 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18474 个服务器的 0%
发布到注册中心的时间比此分类中其他 18474 个服务器的 45% 更新
基础检查结果等于或优于此分类中其他 18474 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Serial Console MCP: AI for telecom equipment and any serial device 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.3.2）于2个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Brontide agent arena

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者：desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

安装

Brontide agent arena

THE MECH ARENA BUILT FOR AI AGENTS. HUMANS WELCOME. Pilot mech duels over MCP, free, no sign-in.

作者：beeswaxpat非常新今天更新

在云端运行✓ brontide.live

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

serial-console-mcp

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

MIT licensed · Python 3.10+ · 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:

Routers and switches. Juniper (Junos) and Cisco (IOS, IOS-XE) console and 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.
Radio transceivers. Icom and Xiegu over CI-V; Kenwood, Yaesu and Elecraft over their text CAT protocols: identify the rig, read and set frequency and mode.
Antenna rotators. Yaesu GS-232 and the many controllers that speak it: read the heading, turn, stop.
Anything else with a serial port. Nothing is tied to telecom: the server 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.

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:

send a command (writes only — doesn't guess when the reply is done), then
read until a prompt appears (# , > , login: …) to capture the whole reply — even a long one — without cutting it off, or
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

Tool	What it does
`list_serial_ports`	Enumerate ports with description and USB hardware id; marks ones open here
`list_presets`	Usual settings per device family: Cisco/Juniper/Linux consoles, full-screen consoles (BIOS, BMC, menus), Kenwood/Elecraft/Yaesu CAT, Icom and Xiegu CI-V, rotators, Arduino, NMEA GPS
`connect` / `reconnect_last` / `disconnect`	Open a port by name. Defaults 9600 8N1, no flow control; baud, data bits, parity, stop bits, RTS/CTS, XON/XOFF, line ending and prompt are all settable, or loaded from a preset. Several ports at once
`send_keys` / `screen`	Press Ctrl-C, Esc, Tab, arrows, F-keys by name; view the VT100/xterm screen of a full-screen console (BIOS, BMC, menu switches, vi)
`send_text` / `send_hex`	Write an ASCII line (CR / LF / CRLF / none) or raw hex bytes. Write-only
`read_until_prompt`	Return buffered output up to a literal or regex prompt, leaving the rest; `auto_reply` pages through `--More--`
`read_available`	Return whatever has arrived, as text and hex
`query_text`	Clear, send, then read until the prompt or until the line goes idle
`expect`	A scripted list of send-and-wait steps in one call: logins, command sequences
`set_lines` / `pulse_line` / `send_break`	Drive DTR and RTS (PTT, Arduino reset), send BREAK
`capture_start` / `capture_stop` / `get_transcript`	Log a session to a file (raw or timestamped TX/RX); re-read the rolling transcript
`port_in_use_by` / `detect_baud`	Which program holds a port; which baud rate produces readable text
`cat_build` / `cat_parse`	Kenwood, Elecraft and Yaesu `;` commands: build a frequency set, decode ID, FA, MD, IF and error replies
`civ_build` / `civ_parse` / `civ_freq`	Icom CI-V frames: build, decode (echo vs reply, BCD frequency, mode, PTT), convert
`rotator_build` / `rotator_parse`	GS-232 rotator commands (read, move, stop, speed) and position replies
`clear_buffer` / `status`	Housekeeping; status shows every open port with control-line states

Ports are opened by name ("rig", "rotator"); tools default to the most recently used one. Each connection has a terminal mode: dumb (raw bytes, the default), ansi (colours and escape sequences stripped, CR/backspace overwrites applied, prompts matched on the line as displayed even after a device redraws it with spaces and backspaces; used by the console presets), or xterm/vt100 (a real screen you can read with screen; needs pip install 'serial-console-mcp[screen]', included in the desktop extension). The receive buffer is capped at 4 MB per port; if a device streams for hours unread, the oldest bytes are dropped and status says how many.

Operating skills

Three skill files in skills/ teach an agent the discipline, the way the fldigi-mcp skills do; copy them into ~/.claude/skills/ or a project's .claude/skills/:

Skill	What it teaches
`serial-console`	The console model, the six rules, terminal modes, keys, presets
`junos-operating`	Junos modes from the prompt (`%` shell, `>` operational, `#` configure), out of the BSD shell and back, `configure exclusive`, `show \	compare`,` commit confirmed`,` rollback`,` cli -c `and` start shell`, health and interface show commands verified on an EX2200 (`show chassis routing-engine`,` show interfaces terse`/`brief`)
`ios-operating`	IOS modes (`>`, `#`, `(config)#`), `enable`/`configure terminal`/`end`, `reload in 10` as the safety net, `write memory`, everyday show commands (`show ip interface brief`, `show processes cpu sorted`)

Environment variables

Variable	Effect
`SERIAL_CONSOLE_READ_ONLY=1`	Refuse writes except read-style commands (`show`, `ID;`, CI-V reads) and refuse control-line changes
`SERIAL_CONSOLE_ALLOW=`	Override the read-only allowlist
`SERIAL_CONSOLE_IDLE_MINUTES=15`	Auto-close a port idle that long (default: never)

Set them in the server's entry in claude_desktop_config.json under "env".

Installing

Download serial-console-mcp.mcpb from the Releases page. The same file works on Mac, Windows and Linux.
In Claude Desktop, go to Settings → Extensions → Advanced settings → Install Extension… and choose the file. A short settings form offers read-only mode and an idle timeout; both are off unless you turn them on.
In a new chat, type: "What serial ports do you see?" If Claude lists your ports, you're done.

No terminal, no Python, nothing to configure by hand.

Upgrading from the 0.3.x `.pkg` or `.exe` installer? Remove the old copy first, or Claude Desktop starts two servers. On a Mac:

"/Library/Application Support/SerialConsoleMCP/serial-console-mcp" configure --remove

sudo rm -rf "/Library/Application Support/SerialConsoleMCP"

On Windows, uninstall Serial Console MCP under Settings → Apps. Then quit and reopen Claude Desktop.

Installing from PyPI

If you already have Python 3.10+ and uv or pipx, you can skip the extension:

uvx serial-console-mcp --version                                   # fetches and runs it

uvx serial-console-mcp configure --command uvx --arg serial-console-mcp

pipx install serial-console-mcp

serial-console-mcp configure --command "$(which serial-console-mcp)"

configure writes a serial-console entry into claude_desktop_config.json (merging with whatever is already there and backing the old file up first). Quit and reopen Claude Desktop. serial-console-mcp configure --remove undoes it. Any other MCP client can launch the same command over stdio.

Installing from source (developers)

git clone https://github.com/sbrunner-atx/serial-console-mcp.git

cd serial-console-mcp uv sync # or: python3 -m venv .venv && . .venv/bin/activate && pip install -e . pytest uv run pytest # fake serial port, no hardware needed uv run serial-console-mcp configure --command "$PWD/.venv/bin/serial-console-mcp"

The package lives in src/serial_console_mcp/: server.py is the MCP server, configure.py the Claude Desktop registrar. manifest.json describes the desktop extension; npx @anthropic-ai/mcpb pack builds it. BUILD.md covers the retired .pkg and .exe installers.

Using it

Plain-English requests work. Some examples:

"List my serial ports."
"Connect to the console on /dev/cu.usbserial-10 at 9600 baud."
"Connect to /dev/cu.BLTH at 38400, 8 data bits, no parity, 1 stop bit, XON/XOFF flow control."
"Connect to the Kenwood with the kenwood-cat preset and call it rig; connect the rotator on the other port."
"Log in as admin and run show version" (one expect call: return, login, password, command).
"What baud rate is this thing?" (detect_baud).
"Key the rig for two seconds" (pulse_line("RTS", 2000), after you confirm).
"Ask the IC-7300 for its frequency" (civ_build, send_hex, read_available, civ_parse).
"What is the TS-590 tuned to?" (query_text("FA;"), cat_parse).
"Turn the rotator to 45 degrees and confirm" (rotator_build, query_text, rotator_parse).
"Record this console session to a file."
"Hit Ctrl-C, that ping is still running." (send_keys)
"Open the BIOS console at 115200 and show me the screen; go down two and press Enter." (screen-console preset, screen, send_keys)
"Reconnect to the same port as last time." (it remembers)
"Send a return, then read until the login prompt."
"Log in as admin and run show interfaces terse, then show me all of it."
"Just read whatever the device is printing right now."
"Disconnect when you're done."

For a router/switch console, tell Claude the prompt it should wait for (often # for enable mode or > for user mode) and it will read until it sees it. For an Icom radio (CI-V), tell Claude — it can send the hex commands those radios expect.

If something doesn't work

"No serial ports found."

Is the device turned on?
Is the USB cable a real *data* cable, not a charge-only one? (A very common gotcha.)
On Windows, open Device Manager and look under Ports (COM & LPT). If nothing's there, Windows needs the cable's driver (often FTDI, CP210x, or CH340).

"Could not open the port" / "access denied."

A serial port can only be used by one program at a time. Close anything else that might be holding it: a terminal (PuTTY/minicom/screen), WSJT-X, your contest logger, the device's own software.

Claude says it can't access serial ports at all.

Make su

只显示了开头部分；其余内容请在仓库中阅读