Install

mq-bridge-app ships in three forms that share one engine and one config format: the CLI / server, the desktop app (UI), and the library. Pick the install path for the form you need. To compile any of them yourself, see BUILD.md.

CLI / server — Homebrew, cargo binstall, cargo install, Docker
Desktop app (UI) — Homebrew cask, or a prebuilt bundle
Library — Rust, Python, Node.js

CLI / server

The CLI (mq-bridge-app) is a single headless binary.

Homebrew (macOS, Linux) — recommended

brew install marcomq/tap/mq-bridge-app
brew upgrade mq-bridge-app     # later, to update

Prebuilt bottles cover Apple Silicon macOS and x86_64 Linux. Homebrew refreshes the tap only on brew update, so if brew upgrade doesn’t pick up a new release yet, run brew update first.

`cargo binstall` — prebuilt binary

Downloads the prebuilt CLI from Releases instead of compiling from source, so it installs in seconds:

cargo binstall mq-bridge-app

Prebuilt binaries are available for x86_64 Linux, Apple Silicon macOS, and x86_64 Windows. (cargo-binstall is a drop-in cargo install replacement.)

`cargo install` — from source

Requires a Rust toolchain and compiles all supported endpoint client libraries (except IBM MQ), so it may take a while:

cargo install mq-bridge-app

For IBM MQ, install the client library first and build with --features=ibm-mq.

Docker

The CLI is published as a multi-arch image (amd64 + arm64):

docker run --rm --name mq-bridge -p 9091:9091 ghcr.io/marcomq/mq-bridge-app:latest

To read+tail from input.log and forward its content, mount the working directory at /app and seed the config from one of the templates baked into the image at /config:

touch input.log
docker run --rm --name mq-bridge -p 9091:9091 -v "$(pwd)":/app \
  ghcr.io/marcomq/mq-bridge-app:latest --init-config=/config/file-to-http.yml

Note

The default latest image is a plain multi-arch image for amd64 and arm64. IBM MQ support is published separately as the latest-ibm-mq and ibm-mq tags on amd64 only, since there is no redistributable IBM MQ client library for arm64 yet. Start that image in emulation mode with --platform=linux/amd64, or build mq-bridge-app yourself with cargo build --release --features=ibm-mq.

Desktop app (UI)

The desktop app is a Tauri bundle of the full messaging workbench — the same UI the CLI serves in a browser, only packaged as a native app.

Homebrew cask (macOS, Apple Silicon)

brew install --cask marcomq/tap/mq-bridge

Homebrew quarantines cask apps by default and the desktop binaries are not notarized yet, so macOS blocks the app on first launch. See the note below for how to open it (via System Settings or Terminal).

Prebuilt bundles (macOS, Windows, Linux)

Bundles for every platform are attached to each release on the GitHub Releases page.

macOS — download the .dmg / .app bundle.
Windows — download the installer or standalone executable.
Linux — download the bundle that suits your distribution: AppImage, .deb, .rpm, or the unpacked archive.

Note

The desktop binaries are currently not notarized, so on macOS Gatekeeper blocks the app on first launch — it’s reported as “damaged” or “cannot be opened because the developer cannot be verified”. This applies to both the Homebrew cask and a downloaded bundle. There are two ways to open it:

Option 1 — System Settings (no Terminal). Try to open the app once so the block is triggered, then go to System Settings → Privacy & Security, scroll to the Security section, and click “Open Anyway” next to the mq-bridge message. Authenticate, then launch the app again.

Option 2 — Terminal. Remove the quarantine attribute directly:
# app in /Applications (where the cask and the .dmg install it)
sudo xattr -rd com.apple.quarantine /Applications/mq-bridge.app
# app in a user-owned directory (e.g. ~/Downloads) — no sudo needed
xattr -rd com.apple.quarantine ~/Downloads/mq-bridge.app
If macOS says the app is “damaged”, the “Open Anyway” button may not appear — use the Terminal method in that case.

Library

Embed the core engine in your own code — produce or consume messages with a unified API, one config format across all three bindings:

Rust — mq-bridge (cargo add mq-bridge)
Python — pip install mq-bridge-py
Node.js — npm install mq-bridge

The core of the library are the MessageConsumer and MessagePublisher traits, found in mq_bridge::traits.

Build from source

Building the CLI/server, the desktop (Tauri) app, or the Docker image from source is covered in BUILD.md. For IBM MQ specifically, see the IBM MQ Setup Guide.

Keyboard shortcuts

mq-bridge