Bussin MCP server

Bussin: Azure Service Bus Explorer

Bussin is a client-side Azure Service Bus explorer. It runs entirely in your browser as a Progressive Web App (PWA). You can access the live version at https://bussin.dev.

Because all connections are established directly from your browser to Azure, there is no backend proxy or intermediate server transiting your credentials or messaging payloads.

Features

• Background Operations: Run connection-safe bulk actions in the background without freezing the user interface.
• Batch Transmissions: Send high-volume message payloads using concurrent AMQP pipelining.
• Bulk Management: Resubmit or delete combinations of active and dead-letter messages with dynamic depth-locking to prevent data loss.
• Namespace Organization: Manage multiple Entra ID environments using folder nesting and text searching.
• Message Search: Search and peek messages using property and body pattern matching.

For visual walkthroughs, screenshots, and detailed guides of these features, visit the website at bussin.dev.

Current Limitations

While Bussin supports most Azure Service Bus operations directly in the browser, there are a few limitations to keep in mind:

• Batch Send on Session-Enabled Entities: Batch sending does not currently support session-enabled queues or topic subscriptions (which require a Session ID for each message).
• Partitioned & Session-Enabled Entities: Certain administrative actions (such as the portal-based fast batch delete/purge API) are not supported by the Service Bus broker on partitioned or session-enabled entities. Bussin automatically falls back to compatible data-plane receiver flows (such as parallel receivers or sequential session loops) in these cases to complete the operation safely.

• Direct Client-Side Architecture: Your data never leaves your browser. Bussin communicates directly with Azure APIs.
• Zero Installation: Access the tool online at https://bussin.dev or install it as a PWA.
• Entra ID Integration: Authenticate securely using your existing Azure identity and Role-Based Access Control (RBAC) roles.

Architecture and Security

Bussin operates under a 100% proxy-free, client-side security model.

When you open Bussin, your browser acts as the direct orchestrator of all network and authentication flows, bypassing intermediate relay servers or third-party databases.

graph TD
    subgraph "Browser Sandbox (100% Client-Side)"
        direction TB
        UI["Blazor WASM UI / Blades"]
        State["ExplorerViewModel & Cache"]
        MSAL["MSAL.js Authentication"]
        
        subgraph "Network Stack"
            ARMClient["ARM HTTP Client"]
            AMQPClient["Rhea AMQP-over-WebSockets"]
        end
    end

    subgraph "Azure Cloud Endpoints"
        direction TB
        AAD["Entra ID"]
        ARM["Azure Resource Manager <br> management.azure.com"]
        ASBData["Service Bus Data Plane <br> namespace.servicebus.windows.net"]
    end

    %% Authentication flows
    MSAL -.->|"1. Authenticate and Consent"| AAD
    AAD -.->|"2. Return Access Tokens"| MSAL
    
    %% ARM Resource Discovery
    UI -->|"Discover Namespaces"| State
    State -->|"3. Query Resources <br> REST + CORS"| ARMClient
    ARMClient -->|"HTTPS GET <br> Auth: Bearer ARM Token"| ARM

    %% Service Bus Data Plane Operations
    State -->|"4. Active Messaging Operations"| AMQPClient
    AMQPClient -->|"WSS Tunnel <br> Bypasses CORS"| ASBData
    AMQPClient -->|"5. CBS Handshake <br> Auth: SB Token"| ASBData

Protocol and Connection Mechanics

Shortened. The full README is on GitHub.