Google Pub/Sub Subscription

Google Pub/Sub Subscription MCP Connector for Claude

A+

This MCP does exactly one thing: it pulls and acknowledges messages from a single Google Pub/Sub Subscription. That's its only function, and nothing else. Incredible for building secure AI workers.

2 tools Official Updated Jun 28, 2026 Official Vinkius Partner

This server strips away dangerous global GCP permissions. It gives your AI agent one surgical superpower: the ability to pull tasks and acknowledge completion on one specific Pub/Sub Subscription.

By strictly scoping access, your AI can safely operate as a highly scalable background worker, processing tasks one by one without ever accessing other subscriptions.

The Superpowers

  • Absolute Containment: The agent is locked to a single subscription. It cannot peek into other workloads or purge queues.
  • Native Pub/Sub Integration: Uses standard polling and acknowledgment mechanisms to ensure tasks are processed reliably.
  • Plug & Play Worker: Instantly turns your AI into an asynchronous background worker capable of chewing through millions of queued tasks.
event-drivenmessage-queueasynchronouspub-subdata-streamingwebhook

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

pull_messages

You MUST acknowledge the messages using their ackIds after you process them, otherwise they will be redelivered. Pull messages from the configured Google Cloud Pub/Sub Subscription

acknowledge_messages

Acknowledge messages to remove them from the Pub/Sub Subscription

See how to talk to your AI agent using Google Pub/Sub Subscription.

Pull the latest 5 messages from the subscription.

I retrieved 2 messages. The first message contains a JSON payload instructing a database backup. Here are their ackIds for when we finish processing.

Process the first message payload and write a summary.

The message data contains an alert about high CPU usage. I have created the summary report as requested.

Acknowledge the messages using these IDs: ["ack123", "ack456"].

Successfully acknowledged 2 messages. They will no longer appear in the queue.

To enforce zero-trust security. An autonomous AI agent pulling its worker tasks should not have access to read messages from unrelated subscriptions, such as system audit logs or financial events.

Related Connectors