Skip to content
Agentmart
Submit a tool

Bussin MCP

MCP server for Azure Service Bus.

Connector by sgebb · GitHub account verified by the MCP Registry

IndexedLicense unknownLocal (stdio)★ 5
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/sgebb-bussin-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

MCP server for Azure Service Bus. Peek, search and replay dead-letter messages from any MCP client.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
6 read · 2 write · 2 delete · 1 not yet classified
Secrets
1 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 11

Read from the source code; the running server may list different tools.

Read 6 · Look things up without changing anything.

  • list_namespaces
  • list_queues
  • list_subscriptions
  • list_topics
  • peek_messages
  • search_messages

Write 2 · Create, change, send or run things.

  • dead_letter_messages
  • send_message

Delete 2 · Delete, drop, revoke or wipe things.

  • delete_messages
  • purge_entity

Not yet classified 1 · We could not tell from the name and description.

  • resubmit_dead_letter

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • YOUR_API_KEY

Tools (11)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • dead_letter_messagesDead-letter messages

    Move active messages to the dead-letter queue by sequence number, with a reason. The messages stop being delivered to consumers and will not be retried, but they are not destroyed: they can be read with peek_messages using fromDeadLetter, and put back with resubmit_dead_letter. Use this to quarantine a poison message rather than delete it. Peek or search first to confirm the sequence numbers. Requires --allow-destructive.

  • delete_messagesDelete specific messages

    Permanently delete messages by sequence number from a queue or its dead-letter queue. This cannot be undone. Peek or search first to confirm the sequence numbers. Requires --allow-destructive.

  • list_namespacesList 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).

  • list_queuesList 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.

  • list_subscriptionsList 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.

  • list_topicsList 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.

  • peek_messagesPeek 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).

  • purge_entityPurge a queue or subscription

    Delete EVERY message from a queue, a subscription, or their dead-letter queue. This is irreversible and unbounded. The confirm argument must be the exact entity name, as a deliberate second step. Requires --allow-destructive.

  • resubmit_dead_letterResubmit dead-lettered messages

    Copy messages out of a queue's dead-letter queue and send them back to that queue. By default this leaves the dead-lettered originals in place, so it is additive and safe to retry; set removeOriginals to also delete them, which additionally requires --allow-destructive. Queues only: resubmitting from a topic subscription's dead-letter queue is not supported here, because Service Bus does not allow publishing straight to a subscription and replaying via the parent topic would copy the message to every other matching subscription. Needs the Data Sender role (or Data Owner), and --allow-send.

  • search_messagesSearch 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).

  • send_messageSend a message

    Send a message to a queue or topic. This is a real send against the live namespace: consumers will pick it up. Sending to a topic delivers a copy to every subscription whose filter matches, so one send can fan out to many consumers. Needs the Azure Service Bus Data Sender role (or Data Owner), and the server must have been started with --allow-send.

Signals

Stars
5
Forks
0
Open issues
0
Last commit (this folder)
Sep 11, 2026 (1 month ago)
Last release
Sep 11, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.sgebb/bussin-mcp
Version
0.1.2
Auth
API key
Packages
npm bussin-mcp
License
License unknown
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Cite this page

Bussin MCP. Agent Mart. https://agentmart.dev/connectors/sgebb-bussin-mcp (last updated 2026-10-24)