mcp-serial-bridge
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_portsA | 接続されているすべてのシリアルポートの情報を返す。 connect の呼び出し前に必ず実行し、利用可能なポート(device名)を確認すること。 macOSでは /dev/cu.* を優先的に返す（/dev/tty.* はカーネル内部用のため除外）。 Returns: list of dict with keys: - device: OS固有の識別子 (例: COM3, /dev/cu.usbserial-10) - description: デバイス名 - hwid: ハードウェアID (VID:PID) |
| connectA | " (CR only, default) " " (CR+LF) " " (LF only) |
| write_and_readA | シリアルポートにコマンドを送信し、応答を受信して返す。 事前に connect を実行しておくこと。 行末には connect で設定した line_ending が自動付加される。 wait_for にプロンプト文字列（例: "> "）を指定すると、 その文字列が受信データに現れるまで待機する。 送受信データはすべてログファイルに記録される。 Args: command: 送信する文字列 wait_for: この文字列が出現するまで受信を待機する（省略可） timeout: 最大待機時間（秒） |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: list_ports enumerates available ports, connect establishes the connection, and write_and_read performs communication over an established connection. There is no overlap or ambiguity between tools.
Tool names are mostly consistent with a verb-oriented style, but 'connect' is a bare verb while 'list_ports' and 'write_and_read' are compound verb phrases. This is a minor deviation and does not cause confusion.
Three tools is perfectly scoped for a serial bridge: discover ports, connect, and exchange data. Each tool is necessary and there are no redundant or extraneous tools.
The core lifecycle (list, connect, communicate) is covered. Minor gaps include the lack of an explicit disconnect operation and limited options for serial parameters (baudrate and line ending only), but these do not break the primary workflow.