Firebase Cloud Messaging (FCM)
Google's Firebase Cloud Messaging delivers free cross-platform push notifications to iOS, Android, and web clients via a single unified API.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Service account JSON keys are long-lived secrets requiring careful management; recommend Workload Identity Federation for GCP-hosted agents to avoid key files entirely. No per-device auth scoping.
⚡ Reliability
Best When
You have a mobile or web app with Firebase SDK installed and need free, scalable push notifications to registered devices.
Avoid When
You need confirmed delivery receipts, SMS fallback for users without your app installed, or carrier-grade message guarantees.
Use Cases
- • Send targeted push notifications to mobile app users when AI agents detect relevant events (price alerts, order status changes)
- • Deliver real-time alerts to field technicians' devices when monitoring systems detect anomalies
- • Notify users of completed async AI processing jobs (document analysis, report generation)
- • Broadcast topic-based notifications to segmented user groups from automated pipeline triggers
- • Trigger silent background data syncs on mobile devices when new agent-generated content is available
Not For
- • SMS delivery to standard phone numbers (FCM is app-push only, not carrier SMS)
- • Guaranteed delivery with receipts where message loss is unacceptable (FCM is best-effort)
- • High-volume transactional messaging to users who haven't installed your app
Interface
Authentication
Uses Google service account JSON key files with OAuth2 access tokens. Legacy server key auth is deprecated. Agents must manage token refresh (1-hour expiry).
Pricing
FCM messaging has no cost. Blaze plan requires a card but FCM sends remain free at any volume.
Agent Metadata
Known Gotchas
- ⚠ Service account OAuth2 tokens expire after 1 hour — agents must implement token refresh or use a library that handles this automatically
- ⚠ Device registration tokens expire and change; agents must handle UNREGISTERED and INVALID_REGISTRATION error codes to prune stale tokens
- ⚠ No delivery receipts by default — agents cannot confirm a notification was actually received/displayed without implementing FCM delivery receipt callbacks in the client app
- ⚠ Notification vs data message distinction is critical: notification messages are handled by OS (may not wake app), data messages require app to be active or use high-priority flag
- ⚠ High-priority messages on Android are subject to Doze mode restrictions and may be delayed; iOS APNs priority mapping is non-obvious and requires testing per device/OS version
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Firebase Cloud Messaging (FCM).
Scores are editorial opinions as of 2026-03-06.