io.github.sgebbPublished by GitHub account sgebbv0.2.0Updated Nov 1, 2026
MCP server for Azure Service Bus. Peek, search and replay dead-letter messages from any MCP client.
MCP server for Azure Service Bus that lets an assistant list namespaces, queues, topics and subscriptions, and peek or search messages, including dead-letter…
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
Azure Service Bus tools for Claude, ChatGPT, Cursor, and any other MCP-aware client.
A Model Context Protocol server that lets an AI assistant inspect your Azure Service Bus queues, topics, subscriptions and dead-letter queues. Peek messages, search payloads and replay failures, using the same AMQP client that powers the Bussin web explorer.
Read-only by default. Nothing writes to your broker unless you say so.
Or run it straight from npx, which is what the client config below does.
Try it with no Azure account at all. --demo runs against an in-process simulator with
seeded queues:
Add to your MCP config (claude_desktop_config.json, or .cursor/mcp.json):
Entra ID is the default and the recommended path. The server uses Azure's
DefaultAzureCredential, so it picks up whatever you already have:
That also works with managed identity, or a service principal via AZURE_TENANT_ID,
AZURE_CLIENT_ID and AZURE_CLIENT_SECRET.
You need two role assignments on the namespace (or its resource group):
A SAS connection string is supported for namespaces your signed-in identity cannot see:
Connection strings authenticate the data plane only. Entity discovery (list_queues and
friends) goes through Azure Resource Manager and needs Entra ID.
The caller is a language model, so anything 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:
purge_entity requires confirmation: the confirm argument must exactly equal the
entity name being purged.resubmit_dead_letter is additive by default: it copies messages back to the source
queue and leaves the dead-lettered originals in place. Removing them additionally requires
--allow-destructive.--search-timeout-ms (default 30s)
rather than hanging the call.list_namespaces: every Service Bus namespace the identity can see, across subscriptionslist_queues: queues with active, dead-letter and scheduled countslist_topics: topics with message countslist_subscriptions: subscriptions under a topic, with countspeek_messages: read messages from a queue, subscription, or dead-letter queuesearch_messages: scan for a body substring, message id, or subject--allow-sendsend_message: send to a queue or topicresubmit_dead_letter: replay dead-lettered messages back to their source queue--allow-destructivedelete_messages: permanently delete specific messages by sequence numberdead_letter_messages: move active messages to the dead-letter queueService Bus only receives deferred messages by sequence number, so both tools lock messages from the
head of the queue up to the requested ones, settle those and release the rest. Their result lists what
was settled and, under notFound, any sequence numbers that weren't.
purge_entity: delete every message from a queue, subscription, or DLQWhich queues in my-namespace have dead-lettered messages?
Show me the last 5 dead-lettered messages on the orders queue and tell me what they have in common.
Search the payments subscription for anything mentioning "timeout" in the last batch.
These three DLQ messages failed on a bug we've now fixed, so resubmit them.
bussin-client-js lives in this repo and is inlined at build time, so the published
package is self-contained and has no file: dependency.
Publishing is driven by a tag, so it is always deliberate:
version in package.jsonThe workflow refuses to publish if the tag and package.json versions disagree, or if
that version is already on npm. It publishes with --provenance, which links the tarball
to the workflow run and commit that produced it.
One-time setup: create an npm automation token with publish rights, add it as the
NPM_TOKEN secret under a repository environment named npm-publish.
To validate without publishing, run the workflow manually with dry_run enabled.
Business Source License 1.1 (BUSL-1.1) — see LICENSE.
Free for personal, educational, and internal business use. Commercial redistribution, rebranding, or hosting this software as a service by third parties is prohibited. Converts to Apache 2.0 on 2029-01-01.
Source: mcp-server/README.md at commit 1fe23e9
List Service Bus namespaces
List the Azure Service Bus namespaces the signed-in identity can see, across all enabled subscriptions. Large tenants can hold dozens, so pass nameFilter whenever you already know roughly what you are looking for. Requires Entra ID sign-in (not available with a connection string).
nameFiltersubscriptionIdList queues
List queues in a namespace with active, dead-letter and scheduled message counts. Use this before peeking so you know which queues have a backlog.
namespaceList topics
List topics in a namespace with their message counts. Messages sit on a topic's subscriptions rather than the topic itself, so follow up with list_subscriptions to find where a backlog actually is.
namespaceList topic subscriptions
List the subscriptions under a topic, with active and dead-letter counts. Use this to pick the subscription to pass to peek_messages or search_messages.
topicrequirednamespacePeek messages
Peek messages from a queue, or from a topic subscription when topic and subscription are given. Peek is non-destructive: it does not lock, consume, or increment delivery count. Set fromDeadLetter to read the dead-letter queue instead of the main entity. This reads from the head of the entity outwards, so it is the right tool for "what is in this queue"; to find particular messages in a backlog, use search_messages instead of paging through peek. Needs the Azure Service Bus Data Receiver role (or Data Owner).
countqueuetopicnamespacefromSequencesubscriptionfromDeadLetterSearch messages
Scan a queue or subscription for messages matching a body substring, message id, or subject. Non-destructive. Scanning is bounded by maxMessages and by a server-side timeout, so on a deep backlog prefer a narrow filter. Returns matching messages with their sequence numbers. Prefer this over repeated peek_messages calls whenever you know something about the messages you want. The sequence numbers it returns are what delete_messages, resubmit_dead_letter and dead_letter_messages take as input. Needs the Data Receiver role (or Data Owner).
queuetopicnamespacebodyFiltermaxMatchesmaxMessagessubscriptionsubjectFilterfromDeadLettermessageIdFilter80% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Declare a license in the repository or the registry entry.
npx -y bussin-mcp --demonpm install -g bussin-mcpnpx -y bussin-mcp --democlaude mcp add bussin -- npx -y bussin-mcp --namespace my-namespace{ "mcpServers": { "bussin": { "command": "npx", "args": ["-y", "bussin-mcp", "--namespace", "my-namespace"] } }}az loginnpx -y bussin-mcp --connection-string "Endpoint=sb://...;SharedAccessKeyName=...;SharedAccessKey=..."npm installnpm run build # builds the Node bundle of bussin-client-js, then bundles with esbuildnpm test # drives the server over stdio against the simulatornpm run typecheck # tsc --noEmitgit tag mcp-v0.1.0 && git push origin mcp-v0.1.0