HARDWARIO CLI Tools

Hardwario CLI is a command-line tool for developing, managing, and debugging devices in the HARDWARIO ecosystem. It supports workflows for CHESTER modules, Nordic SoCs (nRF5x, nRF91, etc.), firmware management, logging, and more.

✨ Features

• Manage CHESTER-specific application SoC features
• Open interactive device console for logs and shell access
• Flash, erase, and reset firmware for supported SoCs
• Work with HARDWARIO's Product Information Block (PIB)
• Support for multiple chip families (nRF51, nRF52, nRF91, etc.)
• Integration with SEGGER J-Link (serial number, speed control)
• Built-in MCP server so AI tools can drive the device console

🛠️ Installation

pip install hardwario

🚀 Quick Start

hardwario --help

Usage: hardwario [OPTIONS] COMMAND [ARGS]...

  HARDWARIO Command Line Tool.

Options:
  --log-level [debug|info|success|warning|error|critical]
                                  Log level to stderr  [default: critical]
  --version                       Show the version and exit.
  --help                          Show this message and exit.

Commands:
  chester  Commands for CHESTER (configurable IoT gateway).
  device   Commands for devices.

🤖 MCP Server (AI Integration)

The device console can expose a built-in Model Context Protocol server, which lets AI tools (Claude, Cursor, etc.) drive the target: send shell commands, read the log, flash firmware, and inspect memory and registers.

The server is off by default. Add --mcp to any console command:

hardwario chester app console --mcp
hardwario device nrf52 console --mcp

It listens on 127.0.0.1:8090 unless --mcp-listen [HOST:]PORT says otherwise.

Claude Code Configuration

Add to your .mcp.json:

{
    "mcpServers": {
        "hardwario-console": {
            "type": "http",
            "url": "http://127.0.0.1:8090/mcp"
        }
    }
}

When the server runs with --mcp-token, add the matching header:

{
    "mcpServers": {
        "hardwario-console": {
            "type": "http",
            "url": "http://127.0.0.1:8090/mcp",
            "headers": {
                "Authorization": "Bearer <TOKEN>"
            }
        }
    }
}

Authentication

The MCP server has no authentication by default and binds to 127.0.0.1, which is fine for local use. Since the tools can flash the device and read or write its memory, set a token whenever the server leaves loopback (e.g. --mcp-listen 0.0.0.0:8090 on a shared debug box):

hardwario device nrf91 console --mcp --mcp-token "$(openssl rand -hex 16)"

Every request must then carry Authorization: Bearer <TOKEN>; anything else gets 401 Unauthorized. Binding off loopback without a token prints a warning. Note the transport is plain HTTP, so on an untrusted network the token is visible on the wire — use an SSH tunnel or a TLS reverse proxy for anything beyond a lab LAN.

Keeping the session alive

Flashing drops the RTT link, which leaves the console dead until it is re-attached. Pair --mcp with --auto-reconnect so the session comes back on its own instead of the AI client having to notice and call reconnect():

hardwario device nrf52 console --mcp --auto-reconnect

Available MCP Tools

License

This project is licensed under the MIT License - see the LICENSE file for details.

Made with ❤  by HARDWARIO a.s. in the heart of Europe.