Azure Service Bus MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_SUBSCRIPTION_ID | No | Azure subscription ID used by servicebus_list_namespaces if set | |
| AZURE_SERVICEBUS_CONNECTION_STRING | No | Connection string for Azure Service Bus, used instead of az login for data plane operations |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| servicebus_list_namespacesA | List all Azure Service Bus namespaces in the current subscription. The subscription is resolved automatically — first from the AZURE_SUBSCRIPTION_ID environment variable, then from the active 'az login' session. If neither is available, an error is returned with instructions. |
| servicebus_list_queuesA | List all queues in an Azure Service Bus namespace. Returns a sorted JSON array of queue names. The namespace can be given as a short name (e.g. shdapps-dev1-eus2-sbn) or as a fully qualified hostname — the .servicebus.windows.net suffix will be appended automatically if missing. |
| servicebus_list_topicsA | List all topics in an Azure Service Bus namespace. Returns a sorted JSON array of topic names. If include_subscriptions is true, returns a JSON object mapping each topic name to a sorted array of its subscription names. The namespace can be given as a short name (e.g. shdapps-dev1-eus2-sbn) or as a fully qualified hostname — the .servicebus.windows.net suffix will be appended automatically if missing. |
| servicebus_send_messageA | Send a single message to an Azure Service Bus queue or topic. The namespace can be given as a short name (e.g. shdapps-dev1-eus2-sbn) or as a fully qualified hostname — the .servicebus.windows.net suffix will be appended automatically if missing. scheduled_enqueue_time accepts an ISO 8601 string (e.g. '2026-03-05T10:00:00Z'). If provided, the message will be enqueued at that time rather than immediately. Auth uses DefaultAzureCredential. Ensure you have run 'az login' before use. |
| servicebus_send_batchA | Send multiple messages to an Azure Service Bus queue or topic in a single batch. Each message in the 'messages' array should have:
The entire batch is delivered in a single send operation. Useful for seeding test data. |
| servicebus_peek_messagesA | Non-destructively peek at messages in an Azure Service Bus queue. Messages are not locked or consumed — this is a read-only operation. Returns message bodies and metadata (sequence number, enqueue time, properties). max_count is capped at 100. For session-enabled queues, provide a session_id to peek a specific session. If session_id is omitted on a session-enabled queue, the next available session is accepted, peeked, and immediately released. Use servicebus_peek_messages_to_file instead if message bodies may be large. |
| servicebus_peek_messages_to_fileA | Non-destructively peek at messages in an Azure Service Bus queue, saving bodies to a file. Message bodies are written to output_file as JSON (keyed by sequence number). Only metadata (sequence number, enqueue time, properties) is returned in context — use this variant when message bodies may be large to avoid filling the context window. For session-enabled queues, provide a session_id to peek a specific session. If session_id is omitted on a session-enabled queue, the next available session is accepted, peeked, and immediately released. |
| servicebus_peek_dlqA | Non-destructively peek at messages in the dead letter queue for an Azure Service Bus queue. Messages are not locked or consumed — this is a read-only operation. Returns message bodies, dead letter reason, error description, and other metadata. max_count is capped at 100. Use servicebus_peek_dlq_to_file instead if message bodies may be large. |
| servicebus_peek_dlq_to_fileA | Non-destructively peek at messages in the dead letter queue for an Azure Service Bus queue, saving bodies to a file. Message bodies are written to output_file as JSON (keyed by sequence number). Only metadata (dead letter reason, error description, sequence number, enqueue time) is returned in context. |
| servicebus_purge_dlqA | Delete all messages from the dead letter queue for an Azure Service Bus queue. THIS IS DESTRUCTIVE — messages cannot be recovered after purging. Stops and leaves remaining messages untouched if the running total exceeds max_messages. |
| servicebus_requeue_dlqA | Move messages from a queue's dead letter queue back to the main queue. Each message is re-sent to the main queue preserving body, session_id, correlation_id, and application_properties, then completed (removed) from the dead letter queue. Stops if the running total would exceed max_messages. |
| servicebus_purge_queueA | Delete all messages from an Azure Service Bus queue. THIS IS DESTRUCTIVE — messages cannot be recovered after purging. Stops and leaves remaining messages untouched if the running total exceeds max_messages. |
| servicebus_peek_subscription_messagesA | Non-destructively peek at messages in an Azure Service Bus topic subscription. Messages are not locked or consumed — this is a read-only operation. Returns message bodies and metadata (sequence number, enqueue time, properties). max_count is capped at 100. For session-enabled subscriptions, provide a session_id to peek a specific session. If session_id is omitted on a session-enabled subscription, the next available session is accepted, peeked, and immediately released. Use servicebus_peek_subscription_messages_to_file instead if message bodies may be large. |
| servicebus_peek_subscription_messages_to_fileA | Non-destructively peek at messages in an Azure Service Bus topic subscription, saving bodies to a file. Message bodies are written to output_file as JSON (keyed by sequence number). Only metadata (sequence number, enqueue time, properties) is returned in context — use this variant when message bodies may be large to avoid filling the context window. For session-enabled subscriptions, provide a session_id to peek a specific session. If session_id is omitted on a session-enabled subscription, the next available session is accepted, peeked, and immediately released. |
| servicebus_peek_subscription_dlqA | Non-destructively peek at messages in the dead letter queue for a topic subscription. Messages are not locked or consumed — this is a read-only operation. Returns message bodies, dead letter reason, error description, and other metadata. max_count is capped at 100. Use servicebus_peek_subscription_dlq_to_file instead if message bodies may be large. |
| servicebus_peek_subscription_dlq_to_fileA | Non-destructively peek at messages in the dead letter queue for a topic subscription, saving bodies to a file. Message bodies are written to output_file as JSON (keyed by sequence number). Only metadata (dead letter reason, error description, sequence number, enqueue time) is returned in context. |
| servicebus_purge_subscriptionA | Delete all messages from an Azure Service Bus topic subscription. THIS IS DESTRUCTIVE — messages cannot be recovered after purging. Stops and leaves remaining messages untouched if the running total exceeds max_messages. |
| servicebus_purge_subscription_dlqA | Delete all messages from the dead letter queue for a topic subscription. THIS IS DESTRUCTIVE — messages cannot be recovered after purging. Stops and leaves remaining messages untouched if the running total exceeds max_messages. |
| servicebus_requeue_subscription_dlqA | Move messages from a topic subscription's dead letter queue back to the topic. Each message is re-sent to the topic preserving body, session_id, correlation_id, and application_properties, then completed (removed) from the dead letter queue. Stops if the running total would exceed max_messages. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BrianDeacon/servicebus-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server