mq-studio

Why MQ Studio

Every broker comes with a console of its own: different pages, different words, and one more service to deploy and keep alive. MQ Studio puts all of them behind the same pages.

• Nothing to deploy. A desktop app for macOS, Windows and Linux. Profiles stay on your machine, and credentials are encrypted at rest.
• One workflow for every broker. Topics, consumers, messages, cluster and alerts work the same way whichever broker you connect to.
• Honest about each broker. Every connection reports what its endpoint can actually do, so a feature the broker lacks is explained rather than faked.
• An assistant beside every page. Ask why a group is behind and it reads the broker to find out, on a model service you choose. It changes nothing until you approve it.
• Open to agents. The same binary serves your connections over MCP: read-only by default, destructive steps confirmed by a person, every write recorded.

A closer look

Ask the assistant

Press ⌘J and ask about what is on screen. The assistant reads the broker with the same tools the MCP server offers, and answers from what it found.

• Your choice of model. Anthropic's API, any OpenAI-compatible service (OpenAI, DeepSeek, Qwen, Kimi and more), or a model on this machine through Ollama or LM Studio. Nothing is sent before you agree to what goes where.
• Writes wait for you. Creating, publishing, resending and moving offsets stop on a card for your approval; emptying and deleting are confirmed every time. Every write is logged.
• Conversations stay on this machine. Encrypted, kept for 30 days by default, and searchable, renamable and exportable from the dock.

docs/ASSISTANT.md covers the setup, what leaves the machine, and what to check when a run fails.

Supported brokers

Broker	Versions	Good to know
RocketMQ	4.x / 5.x	NameServer address; trace, offset reset and clone, ACL
Kafka	3.x / 4.x	Offset resets, ACLs, SCRAM users, quotas, reassignment
RabbitMQ	3.x / 4.x	Management API plus AMQP; browsing requeues what it reads
Pulsar	3.x / 4.x	Tenants and namespaces, cursor moves, role grants
Redis Stream	6.0+	Pending entries, claim and ack; sentinel and cluster
MQTT	3.1.1 / 5.0	Live subscribe; sessions through EMQX-style management APIs
NATS	2.x	JetStream streams and consumers, a core subjects workbench
ActiveMQ	Classic 5.x / 6.xArtemis 2.x	Both products, told apart on connect; browsing takes nothing
NSQ	1.x	Topics and channels across every nsqd; no browse, no DLQ
Amazon SQS	managed	Standard and FIFO; browsing goes through ReceiveMessage
Google Pub/Sub	managed	Subscriptions, snapshots and seek; no backlog figure
Azure Service Bus	managed	Queues, topics and subscription rules; browsing is a peek
Amazon Kinesis	managed	Shards and their lineage; no backlog, browsing uses quota
IBM MQ	9.1+	Queues, topics and channels over mqweb REST; text bodies only
Solace PubSub+	10.x	Message VPNs and subscriptions over SEMP v2; no payloads

docs/DRIVERS.md describes what each driver covers, the wire-compatible systems that connect through an existing one, and how to ask for another.

Download

Get the build for your system at mq-studio.amigoer.com, or from GitHub Releases, which also carries SHA256SUMS.txt and every earlier version.

System	Packages	Requires
macOS	.dmg for Apple silicon and Intel	macOS 12+
Windows	.exe for x64 and ARM64	Windows 10+
Linux	.deb, .rpm and .AppImage for x64 and ARM64	GTK 4 and WebKitGTK 6.0: Ubuntu 24.04+, Debian 13+

macOS builds are not signed by a registered Apple developer yet, so the first launch needs one extra step. The install guide covers it, and every platform's install steps.

Use it from an agent

The same binary is an MCP server, so an agent can work the connections you have already saved:

claude mcp add mq-studio -- "/Applications/MQ Studio.app/Contents/MacOS/mq-studio" mcp

It is read-only unless you allow more when you start it:

• --allow mutate adds creating, publishing and moving offsets; --allow destructive adds emptying and deleting.
• --allow scratch=destructive raises one connection alone, by the name the window shows.
• Emptying and deleting ask a person through the client first, and every write is logged to agent-audit.jsonl.

docs/MCP.md has the details, the setup for other clients, and every tool.

Build from source

Requires Go (the version go.mod pins), Node.js 20.19+ or 22.12+, npm, and the Wails 3 CLI.

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

make check runs what CI runs. CONTRIBUTING.md covers the live tests and how a driver is added.

More

Architecture · Roadmap · Changelog · Releasing · Questions and requests go to GitHub Issues or linux.do (in Chinese).

Apache-2.0 © 2026 amigoer