MCP For Claude Marketplace
Azure Service Bus Queue

Azure Service Bus Queue MCP Connector for Claude

F

This MCP does exactly one thing: it pulls and acknowledges messages from a single Azure Service Bus Queue. That's its only function, and nothing else. Incredible for building secure AI workers.

2 tools Official Updated Jun 28, 2026 Official Vinkius Partner
More Details Connect to Claude

This server strips away dangerous global Azure permissions. It gives your AI agent one surgical superpower: the ability to pull tasks and acknowledge completion on one specific Service Bus Queue.

By strictly scoping access, your AI can safely operate as a highly scalable background worker, processing tasks one by one using Peek-Lock architecture without ever accessing other queues.

The Superpowers

  • Absolute Containment: The agent is locked to a single queue. It cannot peek into other workloads or purge queues.
  • Native Peek-Lock Architecture: Uses standard Peek-Lock and Complete mechanisms to ensure tasks are processed reliably without data loss.
  • Plug & Play Worker: Instantly turns your AI into an asynchronous background worker capable of chewing through millions of queued tasks.
message-queueevent-driventask-processingasynchronous-messagingcloud-messagingworker-patterns

2 tools expose this connector's capabilities to your AI agent.

acknowledge_message

Provide both the messageId and the lockToken. Acknowledge (Complete) a processed message, deleting it from the Queue

pull_message

The message remains hidden from other workers until the lock expires. You MUST call acknowledge_message using the returned messageId and lockToken to confirm you processed it successfully. Pull a single pending message from the configured Azure Service Bus Queue

See how to talk to your AI agent using Azure Service Bus Queue.

Pull a new task from the queue.

I retrieved 1 message. The ID is 'msg_123', the Lock Token is 'lck_abc', and the body contains a request to summarize a report.

I'm done processing. Acknowledge message 'msg_123' with token 'lck_abc'.

The message 'msg_123' has been successfully acknowledged and permanently deleted from the Service Bus Queue.

Peek-Lock is a safety mechanism. If the agent crashes or fails to process the message, the lock will eventually expire, and the message will reappear in the queue for another worker to try. Directly deleting upon reading (Destructive Read) would cause permanent data loss if processing fails.

Related Connectors

PR

PrestaShop MCP

10 tools Official

Bring your PrestaShop store to your AI — orchestrate orders, extract deep product metadata, and track inventory stock levels natively via chat.

A+ View details →
OD

Open Data Euskadi MCP

2 tools Official

Access the official open data portal of the Basque Government — search grants, contracts, news, and execute complex SPARQL queries on Linked Open Data.

F View details →
FD

FDA (openFDA) MCP

12 tools Official

Access public health data via openFDA — search drug labeling, monitor adverse events, and track food recalls directly through your AI agent.

A+ View details →
OP

OpenSea MCP

35 tools Official

Access the world's leading NFT marketplace — query collections, track floor prices, inspect NFT metadata, and monitor wallet balances across multiple chains.

F View details →