ae-hw-bridge
by Vasencheg
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HW_PUPPET_UART_PORT | No | Serial port path for the hw-puppet UART bridge interface (CDC 1: Transparent target console). By default, ae-hw-bridge automatically detects ports in the following priority order: 1. Environment variables HW_PUPPET_CONTROL_PORT / HW_PUPPET_UART_PORT, 2. Standard HW Puppet udev symlinks: /dev/hw-puppet-control / /dev/hw-puppet-uart, 3. Standard Linux CDC fallbacks: /dev/ttyACM0 and /dev/ttyACM1. | |
| HW_PUPPET_CONTROL_PORT | No | Serial port path for the hw-puppet control interface (CDC 0: MicroPython Raw REPL RPC). By default, ae-hw-bridge automatically detects ports in the following priority order: 1. Environment variables HW_PUPPET_CONTROL_PORT / HW_PUPPET_UART_PORT, 2. Standard HW Puppet udev symlinks: /dev/hw-puppet-control / /dev/hw-puppet-uart, 3. Standard Linux CDC fallbacks: /dev/ttyACM0 and /dev/ttyACM1. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues