Azure Service Bus MCP Server

Connect Claude, ChatGPT, Cursor, or any other MCP-aware assistant directly to your Azure Service Bus. Ask which queues are backing up, what the dead-lettered messages have in common, or to replay a batch of failures, instead of clicking through a UI to find out.

bussin-mcp is a free, source-available Model Context Protocol server built on the same AMQP client that powers the Bussin web explorer. It runs locally, authenticates as you, and is read-only until you decide otherwise.

Try it in one command

Demo mode runs against an in-process simulator with seeded queues. No Azure subscription, no sign-in, nothing to clean up afterwards:

npx -y bussin-mcp --demo

When you are ready to point it at a real namespace, sign in with the Azure CLI and drop the flag:

az login
npx -y bussin-mcp --namespace my-namespace

Adding it to your AI client

Claude Code

claude mcp add bussin -- npx -y bussin-mcp --namespace my-namespace

Claude Desktop, Cursor, and other MCP clients

Add the following to your MCP configuration file: claude_desktop_config.json for Claude Desktop, or .cursor/mcp.json for Cursor:

{
  "mcpServers": {
    "bussin": {
      "command": "npx",
      "args": ["-y", "bussin-mcp", "--namespace", "my-namespace"]
    }
  }
}

Restart the client and the Service Bus tools will be available in your next conversation.

What you can ask

Once connected, these are ordinary questions rather than a query language:

• “Which queues in my namespace have dead-lettered messages?”
• “Show me the last five dead-letters on the orders queue and tell me what they have in common.”
• “Search the payments subscription for anything mentioning timeout.”
• “These three DLQ messages failed on a bug we've now fixed, so resubmit them.”
• “How deep is the backlog on each queue right now?”

Safety model

The caller is a language model, so everything irreversible is opt-in. Tools you have not enabled are not registered at all. They are invisible to the model rather than merely refused, so there is nothing to talk it into.

Additional guards

• Peek is genuinely non-destructive. No lock, no consumption, no delivery-count increment.
• Purging requires confirmation. The confirm argument must exactly match the name of the entity being purged.
• Resubmission is additive by default. Dead-lettered originals stay in place unless you also enable destructive operations, so a replay is safe to retry.
• Scans are bounded. Searches and purges stop at a configurable timeout rather than running indefinitely.
• Message bodies are truncated at 4000 characters, so one oversized payload cannot flood the model's context.

Authentication and permissions

Entra ID is the default. The server uses Azure's DefaultAzureCredential, so it picks up an existing az login, a managed identity, or service-principal environment variables. It is the same identity and the same role assignments you already use.

Connection strings are also supported, for namespaces your signed-in identity cannot see. They authenticate the data plane only. Listing entities goes through Azure Resource Manager and needs a real identity.

Why this is a separate program

A reasonable question: Bussin runs in your browser, so why does its MCP server not?

MCP clients connect to a server in one of two ways: by launching a local process and talking to it over standard input and output, or by calling a remote HTTP endpoint. A browser tab is neither. It cannot listen on a port, it cannot be spawned by another program, and it only exists while the tab is open.

So bussin-mcp is a small command-line program that shares Bussin's AMQP client and behaviour but runs on its own. Nothing is sent to a Bussin server in either case: the web app connects from your browser, and the MCP server connects from your machine.

Frequently Asked Questions