Connectors · Email & messaging
Google Cloud Pub/Sub MCP server for AI agents.
actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Cloud Pub/Sub and the rest of your systems. It gives your agent 46 Google Cloud Pub/Sub actions (21 reads, 14 writes and 11 that wait for a confirmation) and holds the Google Cloud Pub/Sub credential itself, so the agent never does. It paces Google Cloud Pub/Sub's limits and records every call. Connecting Google Cloud Pub/Sub needs your own Google Cloud Pub/Sub OAuth app and one admin sign-in.
100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.
claude mcp add --transport http actionlake https://connect.actionlake.com/mcpdo { action: "gcp_pubsub.snapshots.list", intent: "check which Google Cloud Pub/Sub account is connected"}# Projects snapshots: list · read · 1 upstream call- 46actionsin one signed file
- 21readlook, never change
- 14writecreate and update
- 11wait for a yesdestructive, confirmed first
Set up
Connect Google Cloud Pub/Sub in three steps.
- 01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp - 02
Connect Google Cloud Pub/Sub.
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Cloud Pub/Sub, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.
Before the first sign-in, Google Cloud Pub/Sub needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Cloud Pub/Sub app to lend you.
access_tokenAccess token from one sign-in with your own OAuth apprefresh_tokenRefresh token from the same sign-in; the access token is renewed from itclient_idGoogle OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Cloud Pub/Sub API on the…client_secretGoogle OAuth client secret
account { op: "connections.requirements", service: "gcp_pubsub" } # free: exactly what to paste, and what is found for you - 03
Make the first call. Check before a write.
Ask in plain words; Claude picks the action. Before anything changes,
checkvalidates the call and prices it, for free.do { action: "gcp_pubsub.snapshots.list" }# projects snapshots: list · read · 1 upstream callcheck { action: "gcp_pubsub.topics.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent
Google Cloud Pub/Sub at a glance
- Sign-in
- OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Cloud Pub/Sub, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
- You provide
access_tokenrefresh_tokenclient_idclient_secret- Limits we pace to
- 600 calls a minute, per connection
- API covered
- Google Cloud Pub/Sub API v1 (topics, publish, subscriptions, pull/ack, seek, snapshots, schemas, IAM) API pubsub v1 (Discovery revision 20261006)
pubsub.googleapis.com - Built from
- Google Cloud Pub/Sub's documentation, read 23 October 2026pubsub.googleapis.comcloud.google.com
- Service file
- Version 1.0.0, signed (Ed25519)
- Cached reads
- 15 of 21 reads, for up to 5 minutes; a write clears what it affects
- Shared entities
- 1, so ask can line Google Cloud Pub/Sub up with your other systems
- Data
- Processed and stored in Sydney, Australia. No US region yet
Capabilities
What an AI agent can do in Google Cloud Pub/Sub.
46 actions in 6 areas. Every one carries its effect, so a key can allow the reads and hold the rest.
- 21readlook, never change
- 14writecreate and update
- 11destructivewait for a confirmation
Subscriptions
144 read · 6 write · 4 destructive
Projects subscriptions: create · Projects subscriptions: list · Projects subscriptions: test iam permissions · Projects subscriptions: acknowledge
Schemas
137 read · 3 write · 3 destructive
Projects schemas: commit · Projects schemas: create · Projects schemas: list · Projects schemas: list revisions
Topics
94 read · 3 write · 2 destructive
Projects topics: list · Projects topics: create · Projects topics: get · Projects topics: patch
Snapshots
84 read · 2 write · 2 destructive
Projects snapshots: create · Projects snapshots: list · Projects snapshots: test iam permissions · Projects snapshots: get
Topics snapshots
11 read · 0 write · 0 destructive
Projects topics snapshots: list
Topics subscriptions
11 read · 0 write · 0 destructive
Projects topics subscriptions: list
Top actions
The Google Cloud Pub/Sub API, shaped for agents.
The ids your agent types, what each does, and the one name it shares with other systems. 5 of Google Cloud Pub/Sub's 5 action names are shared with at least one other connector, so an agent learns them once.
| Action | What it does | Effect | Same name in |
|---|---|---|---|
gcp_pubsub.topics.listProjects topics: list | Lists matching topics. | read | comm.channel.list27 connectors |
gcp_pubsub.topics.createProjects topics: create | Creates the given topic with the given name. | write | comm.channel.create16 connectors |
gcp_pubsub.topics.deleteProjects topics: delete | Deletes the topic with the given name. | destructive | comm.channel.delete14 connectors |
gcp_pubsub.schemas.listProjects schemas: list | Lists schemas in a project. | read | this connector |
gcp_pubsub.schemas.commitProjects schemas: commit | Commits a new schema revision to an existing schema. | write | this connector |
gcp_pubsub.snapshots.listProjects snapshots: list | Lists the existing snapshots. | read | this connector |
gcp_pubsub.topics.publishProjects topics: publish | Adds one or more messages to the topic. | write | this connector |
gcp_pubsub.snapshots.createProjects snapshots: create | Creates a snapshot from the requested subscription. | write | this connector |
gcp_pubsub.subscriptions.listProjects subscriptions: list | Lists matching subscriptions. | read | this connector |
gcp_pubsub.subscriptions.createProjects subscriptions: create | Creates a subscription to a given topic. | write | this connector |
Try it
Prompts to paste into Claude.
Each one names the Google Cloud Pub/Sub actions it will call, so you know what it reads and what it changes before you send it.
- Readread
Projects snapshots: list in Google Cloud Pub/Sub and tell me what stands out.
calls
gcp_pubsub.snapshots.list - Writewrite
Projects topics: create in Google Cloud Pub/Sub. Show me exactly what you will send before you save it.
calls
gcp_pubsub.topics.create
Governance for Google Cloud Pub/Sub
Destructive actions wait for a yes.
11 Google Cloud Pub/Sub actions are destructive. These are all of them:
- Projects topics: delete
gcp_pubsub.topics.delete - Projects schemas: delete
gcp_pubsub.schemas.delete - Projects snapshots: delete
gcp_pubsub.snapshots.delete - Projects subscriptions: seek
gcp_pubsub.subscriptions.seek - Projects subscriptions: delete
gcp_pubsub.subscriptions.delete - Projects subscriptions: detach
gcp_pubsub.subscriptions.detach - Projects topics: set iam policy
gcp_pubsub.topics.set_iam_policy - Projects schemas: set iam policy
gcp_pubsub.schemas.set_iam_policy - Projects schemas: delete revision
gcp_pubsub.schemas.delete_revision - Projects snapshots: set iam policy
gcp_pubsub.snapshots.set_iam_policy - Projects subscriptions: set iam policy
gcp_pubsub.subscriptions.set_iam_policy
A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.
Projects topics: delete?
intent: the user asked me to projects topics: delete
account { op: "keys.create", name: "gcp-pubsub-agent", allowed_actions: ["gcp_pubsub.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "gcp_pubsub.topics.delete", approver: "[email protected]" }, { match: "gcp_pubsub.schemas.delete", approver: "[email protected]" }, { match: "gcp_pubsub.snapshots.delete", approver: "[email protected]" } ]}Cost
What Google Cloud Pub/Sub costs on actionlake.
Every Google Cloud Pub/Sub action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Cloud Pub/Sub refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
- 1upstream call per actionall 46 Google Cloud Pub/Sub actions
- 7actions pageeach page of a long list is one call
- 15reads can be cacheda cache hit costs nothing
- 100,000calls a month, freepaid plans from US$49 a month for 250,000
Action index
Every Google Cloud Pub/Sub action.
46 actions by area: the id your agent calls, what it does, and its effect.
Subscriptions14
gcp_pubsub.subscriptions.acknowledgeProjects subscriptions: acknowledgewritegcp_pubsub.subscriptions.createProjects subscriptions: createwritegcp_pubsub.subscriptions.deleteProjects subscriptions: deletedestructivegcp_pubsub.subscriptions.detachProjects subscriptions: detachdestructivegcp_pubsub.subscriptions.getProjects subscriptions: getreadgcp_pubsub.subscriptions.get_iam_policyProjects subscriptions: get iam policyreadgcp_pubsub.subscriptions.listProjects subscriptions: listreadgcp_pubsub.subscriptions.modify_ack_deadlineProjects subscriptions: modify ack deadlinewritegcp_pubsub.subscriptions.modify_push_configProjects subscriptions: modify push configwritegcp_pubsub.subscriptions.patchProjects subscriptions: patchwritegcp_pubsub.subscriptions.pullProjects subscriptions: pullwritegcp_pubsub.subscriptions.seekProjects subscriptions: seekdestructivegcp_pubsub.subscriptions.set_iam_policyProjects subscriptions: set iam policydestructivegcp_pubsub.subscriptions.test_iam_permissionsProjects subscriptions: test iam permissionsread
Schemas13
gcp_pubsub.schemas.commitProjects schemas: commitwritegcp_pubsub.schemas.createProjects schemas: createwritegcp_pubsub.schemas.deleteProjects schemas: deletedestructivegcp_pubsub.schemas.delete_revisionProjects schemas: delete revisiondestructivegcp_pubsub.schemas.getProjects schemas: getreadgcp_pubsub.schemas.get_iam_policyProjects schemas: get iam policyreadgcp_pubsub.schemas.listProjects schemas: listreadgcp_pubsub.schemas.list_revisionsProjects schemas: list revisionsreadgcp_pubsub.schemas.rollbackProjects schemas: rollbackwritegcp_pubsub.schemas.set_iam_policyProjects schemas: set iam policydestructivegcp_pubsub.schemas.test_iam_permissionsProjects schemas: test iam permissionsreadgcp_pubsub.schemas.validateProjects schemas: validatereadgcp_pubsub.schemas.validate_messageProjects schemas: validate messageread
Topics9
gcp_pubsub.topics.createProjects topics: createwritegcp_pubsub.topics.deleteProjects topics: deletedestructivegcp_pubsub.topics.getProjects topics: getreadgcp_pubsub.topics.get_iam_policyProjects topics: get iam policyreadgcp_pubsub.topics.listProjects topics: listreadgcp_pubsub.topics.patchProjects topics: patchwritegcp_pubsub.topics.publishProjects topics: publishwritegcp_pubsub.topics.set_iam_policyProjects topics: set iam policydestructivegcp_pubsub.topics.test_iam_permissionsProjects topics: test iam permissionsread
Snapshots8
gcp_pubsub.snapshots.createProjects snapshots: createwritegcp_pubsub.snapshots.deleteProjects snapshots: deletedestructivegcp_pubsub.snapshots.getProjects snapshots: getreadgcp_pubsub.snapshots.get_iam_policyProjects snapshots: get iam policyreadgcp_pubsub.snapshots.listProjects snapshots: listreadgcp_pubsub.snapshots.patchProjects snapshots: patchwritegcp_pubsub.snapshots.set_iam_policyProjects snapshots: set iam policydestructivegcp_pubsub.snapshots.test_iam_permissionsProjects snapshots: test iam permissionsread
Topics snapshots1
gcp_pubsub.topics_snapshots.listProjects topics snapshots: listread
Topics subscriptions1
gcp_pubsub.topics_subscriptions.listProjects topics subscriptions: listread
Questions
The Google Cloud Pub/Sub MCP server, answered.
Is there a Google Cloud Pub/Sub MCP server for Claude?
Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 46 Google Cloud Pub/Sub actions across subscriptions, schemas, topics and snapshots, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Cloud Pub/Sub.
What do I need to connect Google Cloud Pub/Sub?
Your own Google Cloud Pub/Sub OAuth app, registered with Google Cloud Pub/Sub (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Cloud Pub/Sub app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "gcp_pubsub" } lists exactly what to paste.
Can an AI agent delete or change things in Google Cloud Pub/Sub?
Only if its key allows it, and only with an explicit confirmation. 11 Google Cloud Pub/Sub actions are destructive, including projects topics: delete, projects schemas: delete and projects snapshots: delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.
Will an AI agent use up my Google Cloud Pub/Sub API limit?
actionlake paces every call to the limits in the Google Cloud Pub/Sub service file: 600 calls a minute per connection. Repeated reads are answered from cache (15 Google Cloud Pub/Sub actions can be), which never reaches Google Cloud Pub/Sub.
What does a Google Cloud Pub/Sub action cost?
One upstream call, the only unit actionlake bills. A list that pages bills one call per page (7 Google Cloud Pub/Sub actions page). Cache hits, searches, dry runs and calls Google Cloud Pub/Sub refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.
Which Google Cloud Pub/Sub API does it cover?
The Google Cloud Pub/Sub API v1 (topics, publish, subscriptions, pull/ack, seek, snapshots, schemas, IAM) API pubsub v1 (Discovery revision 20261006) at pubsub.googleapis.com. It is built from Google Cloud Pub/Sub's documentation as read on 23 October 2026. 46 actions in 6 areas, each one in the signed service file (version 1.0.0).
Does actionlake keep my Google Cloud Pub/Sub data, and where?
actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Google Cloud Pub/Sub credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.
Which AI clients can use it?
Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.
Give your agent Google Cloud Pub/Sub today.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.