Fast tree browsing
Subscriptions, namespaces, queues, topics — indexed locally in SQLite. Navigation is instant, even on enterprise tenants with thousands of resources.
The fastest way to debug your Azure Service Buses
Search, inspect, edit, and resend messages in seconds — with custom dead-letter alerts and MCP-powered debugging built in.
Free · v0.7.1 · no account, no telemetry
Built for the way developers actually use Service Bus.
Everything you'd want Service Bus Explorer to be, without the legacy baggage.
Browse and act on messages
Peek active and dead-letter messages without dequeuing. Filter by session, ID, subject, or DL reason. Edit a body before resending, compose new messages, or drain a queue with a confirmed bulk action — purge, send-all-to-DL, or empty an entire DLQ.
New
Set up automatic monitoring and alerting
Pick exactly which queues, topics, and subscriptions to watch, and which ones should alert. Runs in the background at a low cost to your machine.
Spotlight search
Ctrl+I opens a system-wide fuzzy search across every indexed resource. Stays active even with viewbus closed to the tray.
Built-in MCP server
Ships a Model Context Protocol server so Claude, ChatGPT, or any MCP-aware AI can list namespaces, search resources, peek queues, and fetch full messages.
viewbus-mcp
$ viewbus-mcp --list-tools
10 read-only tools · 1 opt-in write tool
get_status index state + last refresh
list_namespaces azure subscription namespaces
list_queues queues in a namespace
list_topics topics in a namespace
list_subscriptions subs under a topic
get_resource full detail for a resource
search_resources fuzzy across names + paths
count_messages active + dead-letter totals
peek_messages read without dequeuing
get_message_detail body + properties by seq no.
upsert_theme write · opt-in via settings
Built-in themes & VS Code import
Six built-in dark and light themes — including a warm Clave theme. One-click importer pulls your active VS Code theme into viewbus.
How it compares
The classic Service Bus Explorer is Windows-only; the Azure Portal can't search across resources or alert you. Here's where viewbus fits — and where the others still win.
| viewbus | Service Bus Explorer | Azure Portal | |
|---|---|---|---|
| Native app for Mac & Windows | Windows only | In-browser | |
| Search message bodies across queues, topics & subscriptions | — | — | |
| Edit & resend, with a side-by-side diff | Limited | — | |
| Alerts when a queue or subscription crosses a threshold | — | — | |
| AI assistant access (MCP server) | — | — | |
| Relay, Event Hubs & Notification Hubs | — | — | |
| Price | Free | Free | Free |
On the roadmap
Free, and shipping often. A few things already in the works:
-
Dead-letter trends
History and sparklines per resource, so you can spot a backlog that started building two days ago — not just right now.
-
More message formats
Syntax-highlighted XML, YAML, and protobuf bodies — not just JSON and plain text.
-
Local emulator support
Point viewbus at the local Azure Service Bus emulator for development, right beside your real namespaces.
-
Theme marketplace
Browse and one-click-install community-made viewbus themes, share your own, and export your full setup to move between machines.
Most requested
Request a feature →Open any request to upvote it on GitHub — the most-wanted ship first.
Your data never leaves your machine.
No backend, no telemetry, no account. When you sign in, it's to your own Azure — not to viewbus. Tokens and connection strings stay in your OS keychain, never on disk in plain text.
We can't see your namespaces or your messages, and we're not training any AI on what you do. Don't take our word for it — open the network inspector and see exactly where traffic goes.
network · outbound
→login.microsoftonline.comsign-in
→management.azure.comyour subscriptions
→*.servicebus.windows.netyour messages
→viewbus.app/latest.jsonupdate check
✓ no telemetry · no analytics · no account
✓ nothing about you is ever uploaded