MCP For Claude Marketplace
Azure Service Bus Queue

Azure Service Bus Queue MCP Connector for Claude

A+

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 Oct 1, 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

Conversation State Machine

Conversation State Machine MCP

3 tools Official

Enforce structured, deterministic conversation flows for AI agents.

A+ View details →
Task Completion Enforcer Prover

Task Completion Enforcer Prover MCP

1 tools Official

An AI was asked to build 5 API endpoints, write tests, and update documentation. It built 3 endpoints, left TODO comments in the tests, never touched the documentation, and declared 'Done! Let me know if you need anything else.' The user spent 40 minutes finding the gaps. This happens every single day, on every LLM, in every coding session. This tool forces five completion axes: requirement extraction, completion evidence, gap identification, continuation execution, and final verification against the original request.

A+ View details →
Symbl.ai

Symbl.ai MCP

9 tools Official

Extract conversation intelligence from audio, video, and text — get summaries, action items, and topics directly from any AI agent.

A+ View details →
Zeplo (Queue & Background Job API)

Zeplo (Queue & Background Job API) MCP

17 tools Official

Schedule, queue, and manage background jobs and webhooks via Zeplo directly from your AI agent.

A+ View details →