What can you do with the Google Pub/Sub integration?

LiveContext exposes 23 operations on Google Pub/Sub, covering subscription, topic, schema and snapshot. Common uses include automate topic management, automate subscription management and automate schema management.

Which OAuth scopes does Google Pub/Sub require?

The operations that declare a scope all need https://www.googleapis.com/auth/pubsub.

LiveContext

All integrations

Google Pub/Sub integration

Google Cloud Pub/Sub messaging service API for reliable, scalable, asynchronous messaging between services. Create topics and subscriptions, publish and pull messages, manage schemas, and configure push delivery endpoints.

23 toolsOAuthAPI docs

Connect Google Pub/Sub How integrations work

Common Google Pub/Sub use cases

automate topic management
automate subscription management
automate schema management
automate snapshot management
get topic programmatically
get schema programmatically
list topic programmatically
list schema programmatically
create topic programmatically
delete topic programmatically

What you can do with Google Pub/Sub

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Subscription, 5 operations

PUTcreate_subscription
Creates a new subscription to a given topic. If the subscription already exists, returns ALREADY_EXISTS
DELETEdelete_subscription
Deletes an existing subscription. All pending messages in the subscription are immediately dropped
GETget_subscription
Gets the configuration details of a subscription
GETlist_subscriptions
Lists matching subscriptions in the given project
PATCHupdate_subscription
Updates an existing subscription. Only the fields set in the request body are updated

Topic, 5 operations

PUTcreate_topic
Creates a new topic with the given name
DELETEdelete_topic
Deletes the topic with the given name. Existing subscriptions are not deleted but their topic field is set to _deleted-topic_
GETget_topic
Gets the configuration of a topic
GETlist_topics
Lists matching topics in the given project
PATCHupdate_topic
Updates an existing topic. Only the fields set in the updateMask are modified

Schema, 4 operations

POSTcreate_schema
Creates a new schema in the given project for validating published messages
DELETEdelete_schema
Deletes a schema by name. All schema revisions are deleted as well
GETget_schema
Gets a schema by name. Get schema.
GETlist_schemas
Lists schemas in the given project

Snapshot, 3 operations

PUTcreate_snapshot
Creates a snapshot from the requested subscription. Snapshots are used in seek operations to restore subscription state
DELETEdelete_snapshot
Removes an existing snapshot. Snapshots are used in seek operations
GETlist_snapshots
Lists the existing snapshots in the given project

Ack deadline, 1 operation

POSTmodify_ack_deadline
Modifies the ack deadline for specific messages. Useful to indicate that more time is needed to process a message

Acknowledge message, 1 operation

POSTacknowledge_messages
Acknowledges messages that have been pulled so they will not be delivered again

Message, 1 operation

POSTpublish_messages
Publishes one or more messages to a topic. Returns message IDs for each published message

Pull message, 1 operation

POSTpull_messages
Pulls messages from the server. Returns an empty list if there are no messages available

Seek subscription, 1 operation

POSTseek_subscription
Seeks a subscription to a given point in time or to a snapshot, causing messages to be redelivered or acknowledged in bulk

Topic subscription, 1 operation

GETlist_topic_subscriptions
Lists the names of subscriptions attached to the specified topic

OAuth scopes Google Pub/Sub requires

Each operation declares the scopes Google Pub/Sub requires for it.

https://www.googleapis.com/auth/pubsubneeded by acknowledge_messages, create_schema, create_snapshot and 20 more

Use Google Pub/Sub from Claude Code, Cursor or Codex

Connect Google Pub/Sub in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Pub/Sub operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google Pub/Sub

Create your workspace
Sign up free. Nothing to install.
Connect Google Pub/Sub once
Add your Google Pub/Sub connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Google Pub/Sub integration FAQ

What can you do with the Google Pub/Sub integration?: LiveContext exposes 23 operations on Google Pub/Sub, covering subscription, topic, schema and snapshot. Common uses include automate topic management, automate subscription management and automate schema management.
Which OAuth scopes does Google Pub/Sub require?: The operations that declare a scope all need https://www.googleapis.com/auth/pubsub.