Repolode
Submit
amigoer

amigoer/mq-studio

A local-first desktop client that manages RocketMQ, Kafka, RabbitMQ, Pulsar, Redis Stream, NATS and other message brokers through one interface.

View on GitHubWebsite
Stars
97
Forks
8
Open issues
1
Last commit
2 days ago

What is it?

MQ Studio is a cross-platform desktop app for inspecting and operating message brokers. Each broker normally ships with its own console, and this project puts topics, consumer groups, messages, cluster status and alerts behind the same pages, so one workflow works across RocketMQ, Kafka, RabbitMQ, Pulsar, Redis Stream, MQTT, NATS, ActiveMQ, NSQ and several managed cloud services. Nothing needs to be deployed on a server, and connection profiles and credentials are stored locally with encryption at rest.

Each connection reports which operations its endpoint actually supports, so missing broker features are shown as unavailable rather than simulated. A built-in assistant can answer questions about what is on screen by querying the broker, using a model service the user chooses, including Anthropic, OpenAI-compatible APIs, Ollama or LM Studio. Write actions such as publishing or moving offsets wait for user approval.

The same binary can also run as an MCP server so agents can work with saved connections. It is read-only by default, and destructive operations require explicit permission and confirmation, with writes recorded in an audit log. The app is built with Go and Wails, with a React frontend, and is distributed for macOS, Windows and Linux.

Key features

  • 01Manages topics, consumer groups, messages and cluster health across many brokers in one UI.
  • 02Supports RocketMQ, Kafka, RabbitMQ, Pulsar, Redis Stream, MQTT, NATS, ActiveMQ, NSQ and several managed cloud queues.
  • 03Stores connection profiles and credentials locally with encryption.
  • 04Shows only the operations each broker endpoint actually supports.
  • 05Includes an assistant that inspects the broker and asks for approval before any write.
  • 06Runs as an MCP server for agents, read-only by default.

Use cases

  • Debugging why a Kafka or RocketMQ consumer group is lagging behind.
  • Browsing or searching messages on a RabbitMQ or Pulsar topic during development.
  • Comparing and operating several brokers from one tool instead of separate consoles.
  • Letting an AI agent inspect saved message queue connections under controlled permissions.

Quick start

  1. 1

    Download the app for your system from the releases page or the project website

  2. 2

    Install the Wails 3 CLI

    go install github.com/wailsapp/wails/v3/cmd/wails3@latest
  3. 3

    Install dependencies from source

    make install
  4. 4

    Start the app in development mode

    make dev

Things to know

  • Building from source requires Go, Node.js and the Wails 3 CLI.
  • macOS builds are not signed by a registered Apple developer, so the first launch needs an extra step.
  • Linux builds require GTK 4 and WebKitGTK 6.0, which need recent Ubuntu or Debian versions.
  • The assistant needs a model service you choose, which may be a paid API key.

In collections

Desktop GUI apps & toolkits

Topics

#message-queue#kafka#rocketmq#rabbitmq#desktop-app#mqtt#redis-streams#golang#cross-platform#devtools

FAQ

What is mq-studio?
A local-first desktop client that manages RocketMQ, Kafka, RabbitMQ, Pulsar, Redis Stream, NATS and other message brokers through one interface. MQ Studio is a cross-platform desktop app for inspecting and operating message brokers. Each broker normally ships with its own console, and this project puts topics, consumer groups, messages, cluster status and alerts behind the same pages, so one workflow works across RocketMQ, Kafka, RabbitMQ, Pulsar, Redis Stream, MQTT, NATS, ActiveMQ, NSQ and several managed cloud services. Nothing needs to be deployed on a server, and connection profiles and credentials are stored locally with encryption at rest.
Is mq-studio free to use? What license does it have?
mq-studio is open source under the Apache-2.0 license. Check the license terms before using it in commercial products.
Is mq-studio still maintained?
Actively maintained. The last commit to mq-studio was on Oct 21, 2026.
What can I use mq-studio for?
Debugging why a Kafka or RocketMQ consumer group is lagging behind. Browsing or searching messages on a RabbitMQ or Pulsar topic during development. Comparing and operating several brokers from one tool instead of separate consoles. Letting an AI agent inspect saved message queue connections under controlled permissions.
How do I install mq-studio?
Download the app for your system from the releases page or the project website Install the Wails 3 CLI: go install github.com/wailsapp/wails/v3/cmd/wails3@latest Install dependencies from source: make install Start the app in development mode: make dev
Where can I get mq-studio?
The source code and installation instructions are on GitHub: https://github.com/amigoer/mq-studio

Summary generated by AI from the project's README. GitHub stats refresh daily.

Related projects