Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Read-only tools for COM ports, Modbus, MC and SCPI on Windows, plus writes to local simulators only
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。
在终端中运行这条命令
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 portdock 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.11.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Zendesk
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Zendesk MCP Pack — tickets, users, organizations via OAuth.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
한국어
Free communication tools for testing field hardware on Windows. Each tool is a separate, small download; they share the same communication and decoding core.
| Tool | What it does |
|---|---|
| PortDock Serial | Serial (COM) terminal — RS-232/RS-485/USB serial, signal lines (DTR/RTS/CTS/DSR/RI/CD), auto-reconnect after a USB replug, framing, checksums (nine types plus custom CRC), Modbus RTU decoding and request builder, auto-reply, timestamped test logs; from 0.10.0 port sharing (COM ↔ TCP, raw or RFC 2217, TCP 7000 on 127.0.0.1 by default), a Modbus TCP ↔ RTU gateway (SCADA/HMI over Modbus TCP to RS-485 devices, TCP 502 on 127.0.0.1 by default, one request at a time, timeout → exception 0B, unit ID 0 answered with exception 0A unless you choose RTU broadcast — and, with an allowed-unit list, list 0 in it) and Modbus RTU listen-only sniffing (CRC framing, request/reply pairs, reply times) |
| PortDock Modbus Slave | Modbus slave simulator over serial RTU, Modbus TCP or RTU over TCP — coil and register tables (32-bit, float and string cells), value simulation (from 0.10.0 also noise — a slow random drift within limits), fault injection, built-in device profiles (from 0.10.0 «Emulate device…» with live values — run command → output frequency ramp, energy accumulation — read-only/write-only enforcement and exception 02 for addresses not in the map), CSV register maps, and the master's requests as they arrive. Modbus TCP listens on the address you choose (from 0.10.0 127.0.0.1 on first run — pick 0.0.0.0 or an adapter's address for a master on another PC) |
| PortDock TCP | TCP client, server and relay (monitor) — multiple peers, echo, auto-reconnect, Modbus TCP framing, relay capture saved as pcapng (open in Wireshark), Modbus TCP and MC request/reply pairs with response time and no-reply count |
| PortDock UDP | UDP sender/receiver — broadcast, multicast, echo |
| PortDock Simulator | Rule-based fake device over serial, TCP and UDP — "when this arrives, reply with that" |
| PortDock Net Scan | Find devices on an industrial network: ping/ARP sweep, MAC vendor, industrial ports (Modbus 502, MC, XGT …), long-term ping monitor, Wake-on-LAN; from 0.10.0 named baselines — compare a scan with a saved device list (new, missing, MAC changed, IP changed, open ports changed; CSV); from 0.10.0 exposure notes when an industrial protocol without authentication (Modbus, MC, EtherNet/IP, S7, OPC UA) or Telnet/HTTP is among the open ports — no extra scanning; from 0.11.0 broadcast discovery on request — EtherNet/IP ListIdentity (UDP 44818) and BACnet Who-Is (UDP 47808) to the selected adapter's broadcast address: vendor, device type, product name and revision / device instance, vendor ID and max APDU (serial numbers not shown) |
| PortDock Modbus Master | Modbus RTU/TCP master (poll tool): several poll tables, typed values (U16–F64, strings, byte orders, 40001 notation), writes 05/06/0F/10, slave ID and address range scan, built-in device profiles, decoded traffic, statistics, CSV value log, trends; from 0.10.0 line-settings search (unknown baud/parity/ID — a short read per combination, never ID 0), a «no response» possible-causes panel (no bytes, echo only, CRC errors, truncated frames, exceptions, other ID), device settings backup, compare and restore (JSON/CSV, preview and read-back check before/after writing) and value watch and alarms (low/high limits with hysteresis, stuck N s, communication lost N s; alarm list with acknowledge, optional sound, alarm CSV log — a monitoring aid, not a safety device) |
| PortDock SCPI | SCPI instrument terminal over LAN socket (5025) or RS-232, no VISA: query/write/read with response times, *IDN? identification, error queue draining, *OPC? waits, repeated numeric measurements (table, trend, CSV), block data (#…) with HEX preview and file save |
| PortDock Plot | Live plotter for numbers from serial, TCP or UDP: comma/space/tab/semicolon text (auto-detected), Arduino-style name:value, header names, binary frames (start bytes, u8–f64, endianness, checksum); up to 32 channels on left/right axes, pause, cursor, two-point Δt/Δvalue, zoom; statistics, CSV recording while receiving, CSV/PNG export; from 0.10.0 per-channel watch and alarms (limits, stuck, data lost) |
| PortDock Port Inspector | Read-only COM port inspector, no administrator rights: device and driver (provider, version, date, INF), Device Manager problem code with its meaning and what to try, USB chip from VID/PID (FTDI, Prolific, WCH, Silicon Labs …), device settings such as the FTDI latency timer, USB power saving, plug and driver history from the event logs, COM number reservations (orphan and duplicate numbers); TX–RX loopback test per baud rate (lost/changed bytes, round-trip ms) and 2-wire RS-485 echo check; from 0.10.0 a two-port test (two adapters wired to each other, both directions), patterns (0x00–0xFF, 0x55/0xAA) and a text wiring diagram — also in Serial «Check connection…»; from 0.10.0 «Compare with last time» (save the check and later see only what changed: COM number, driver version/date, USB location, adapter and PC settings, new blue screens — no serial numbers stored). Also tabs for this PC's network adapters (link speed, duplex, jumbo frames and power saving, with a GigE camera mode), equipment-PC Windows settings (fast startup, sleep, update restarts, time sync, unexpected shutdowns; from 0.10.0 blue screens and sudden shutdowns — stop codes, Kernel-Power 41, EventLog 6008, Minidump files only counted —, NVMe storage health, what woke the PC from sleep, battery capacity and a field PC exposure check — Remote Desktop/NLA, SMBv1, firewall profiles, ports listening on all addresses, automatic sign-in, USB AutoPlay) and wireless (Wi-Fi adapter power saving and disconnect history, Bluetooth adapter, services and hands-free audio). Text/JSON export. It never changes settings |
| PortDock PLC Simulator | MC protocol (SLMP) server simulator, implemented from Mitsubishi Electric's public manuals (not affiliated; behaviour may differ from a real PLC) — 3E/4E frames, binary/ASCII, TCP server or UDP, batch and random read/write and loopback, 18 devices (D, W, R, ZR, M, X, Y, B, L, SM, SD …) with hex numbering for X/Y/B/W/ZR, end-code error replies, fault injection, value simulation, JSON save/load. From 0.10.0 it can also answer the LS ELECTRIC XGT dedicated protocol (FEnet, TCP 2004 / UDP 2005 — individual and continuous read/write of %MW·%MX·%DB… variables, from LS ELECTRIC's public manuals, not affiliated). Listens on 127.0.0.1 by default; «Allow other PCs to connect (0.0.0.0)» opens it to the network. |
| PortDock Hardware Tester | Wi-Fi, Bluetooth and USB recorder for Windows PCs, read-only and without administrator rights: only while recording, pings the gateway and one internet address side by side (latency, loss, jitter) with DNS response time and the Wi-Fi disconnect reasons Windows logs on one timeline, a «router side / beyond the router» summary that says where to look, CSV export; a log of when paired Bluetooth devices connect and disconnect (names shown on screen only), Bluetooth audio mode (stereo or hands-free) with left/right test tones, and on request the Wi-Fi signal, link speed, band and channel with nearby networks counted per channel (location permission on Windows 11 24H2 and later; network names never read); from 0.10.0 a USB connect/disconnect log (device notifications plus a list check every 3 s; name, VID:PID, hub port and speed; «suspected repeated drops» at 3 drops within 10 minutes, USB 3 devices running at USB 2.0 speed, «Earlier records» from the Kernel-PnP log — device serial numbers are never shown, copied or saved). For keyboard, mouse, monitor, speaker, microphone, webcam and gamepad tests, use the PC hardware tests on the website (browser, no install). |
| PortDock MCP | MCP server for AI clients (Claude Desktop, VS Code, Cursor …), no window, stdio: lets the AI *read* COM ports and the Port Inspector report, listen on a serial port (sends nothing), read Modbus (FC 01–04), MC protocol 3E (0401) and SCPI queries, ping, network adapters and the built-in device register maps. The two write tools accept only 127.0.0.1 (this PC), for practising with simulators; from 0.10.0 modbus_write_sim also writes only after the target's vendor name begins with «PortDock» (Read Device Identification, FC 2B/0E — as PortDock Modbus Slave does by default), so a forwarder to a real device such as PortDock Serial's Modbus TCP ↔ RTU gateway (127.0.0.1:502 by default) is refused. mc_write_sim is checked by address only (the Serial gateway passes Modbus only), so do not use it while a program on this PC forwards to another device (TCP relay, gateway, tunnel). Every call is kept in a local session log. Details: docs/mcp.md |
All twelve apps: the «AI» button in the header copies the current situation (connection settings, errors, recent traffic or check results) to the clipboard as text to paste into an AI chat. PortDock sends nothing (user folders, PC names, the last part of MAC addresses and public IPs are hidden).
Screen languages: 12 — Korean, English, Japanese, German, Spanish, Portuguese (Brazil), Polish, French, Vietnamese, Turkish, Italian and Indonesian. The first start follows the Windows display language (any other language starts in English); change it in the header or Settings. Help comes in Korean and English, so other screen languages show the English help.
Website: https://portdock.dev
Get the latest version from [GitHub Releases](https://github.com/portdock/PortDock/releases/latest). File names never change, so these links always point to the newest release:
| Modbus Master | [PortDock-Modbus-Master-setup.exe](https://github.com/portdock/PortDoc
只显示了开头部分;其余内容请在仓库中阅读