bxnxm/micros-mcp repository overview

⁠micrOSMCP

micrOSMCP⁠ is a standalone Model Context Protocol server and HTTPS tester UI for discovering and controlling micrOS⁠ devices.

The image provides two modes: mcp for stdio MCP clients and ui for the HTTPS tester with optional OpenAI chat, speech, and microphone input.

⁠Stdio MCP Server

docker run --rm -i \
  -e MICROS_NETWORK_PREFIX=10.0.1 \
  -v micros-mcp-data:/app/data \
  bxnxm/micros-mcp:latest mcp

⁠HTTPS Tester UI

docker run -d \
  --name micros-mcp-ui \
  -p 3333:3333 \
  -e MICROS_NETWORK_PREFIX=10.0.1 \
  -e MICROS_UI_CERT_HOSTS=gateway.local,10.0.1.42 \
  -v micros-mcp-data:/app/data \
  bxnxm/micros-mcp:latest ui

Open https://gateway.local:3333 or https://10.0.1.42:3333.

MICROS_UI_CERT_HOSTS is effectively required for access through the Docker host. Include every IP address or DNS hostname users will enter in their browsers. Publishing port 3333 makes the UI reachable, but it does not add the Docker host's address to the HTTPS certificate.

The UI stores its self-signed certificate under /app/data. Keep the volume mounted and accept or trust ui-self-signed-cert.pem on client devices to enable browser microphone access.

⁠Configuration

• Set MICROS_NETWORK_PREFIX to the LAN /24 prefix containing the micrOS devices, such as 10.0.1. Docker cannot reliably auto-detect the host LAN.
• Ensure the container can reach micrOS devices on TCP port 9008.
• Changing MICROS_UI_CERT_HOSTS regenerates the certificate, which clients must trust again.

Create the persistent volume once:

docker volume create micros-mcp-data

⁠MCP Client Configuration

{
  "mcpServers": {
    "microsmcp": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-e", "MICROS_NETWORK_PREFIX=10.0.1",
        "-v", "micros-mcp-data:/app/data",
        "bxnxm/micros-mcp:latest", "mcp"
      ]
    }
  }
}

See the GitHub repository⁠ for tool documentation and native installation instructions.