Integration

Firebase Cloud Messaging integration

Firebase Cloud Messaging (FCM) REST API for push notifications. Send messages to individual devices, topics, or device groups. Manage topic subscriptions and retrieve device token information for mobile and web applications.

Connect Firebase Cloud Messaging How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Firebase Cloud Messaging.Built from the 6 Firebase Cloud Messaging tools below, on the connection you add once.

Common Firebase Cloud Messaging use cases

topic management
token validation
broadcast messages
push notifications
targeted messaging
news alerts
user alerts
debug messaging
unsubscribe users
user segmentation

What you can do with Firebase Cloud Messaging

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.

get_token_infoGet token infoGETRetrieves metadata about an FCM registration token including topic subscriptions.
send_messageSend messagePOSTSends a push notification message to a device token.
send_to_conditionSend to conditionPOSTSends a notification to devices matching a topic condition expression.
send_to_topicSend to topicPOSTSends a push notification to all devices subscribed to a topic.
subscribe_to_topicSubscribe to topicPOSTSubscribes multiple device tokens to a topic for group messaging.
unsubscribe_from_topicUnsubscribe from topicPOSTUnsubscribes multiple device tokens from a topic.

Firebase Cloud Messaging API rate limits

100 requests per second

FCM topic subscriptions limited to 3000 QPS per project.

These are the limits Firebase Cloud Messaging documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Firebase Cloud Messaging documentation for current values.

Use Firebase Cloud Messaging from Claude Code, Cursor or Codex

Connect Firebase Cloud Messaging in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Firebase Cloud Messaging 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 Firebase Cloud Messaging

Create your workspace
Sign up free. Nothing to install.
Connect Firebase Cloud Messaging once
Add your Firebase Cloud Messaging 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.

Firebase Cloud Messaging integration FAQ

What can you do with the Firebase Cloud Messaging integration?

LiveContext exposes 6 operations on Firebase Cloud Messaging, covering cloud messaging. Common uses include topic management, token validation and broadcast messages.

What are the Firebase Cloud Messaging API rate limits?

Firebase Cloud Messaging documents 100 requests per second. FCM topic subscriptions limited to 3000 QPS per project. Limits are set by Firebase Cloud Messaging and can depend on your plan.