Skip to main content
Use sendrealm-push when an agent needs to add, review, or debug Sendrealm push notifications. The skill covers both sides of push: device registration in apps and backend sends from trusted code.

​
What It Covers

  • Choosing the right SDK for Web, React Native Expo, React Native bare, Android, or iOS.
  • Configuring Firebase, APNs, or Web Push provider settings in Sendrealm.
  • Initializing device SDKs with public Sendrealm Push App IDs.
  • Requesting permission from a user action and linking users with login.
  • Sending notifications from trusted backend code with @sendrealm/sdk.
  • Using exactly one target style per send: tokens, web_subscriptions, device_ids, contact_ids, external_ids, emails, or audiences.
  • Debugging registration, environment, credentials, diagnostics, and delivery issues.
  • Testing through MCP or the API by discovering a real device, sending one explicit test, and polling provider/client events.

​
Use It

The skill should ask for the Sendrealm Push App ID, app environment, provider setup status, target identity, and final notification copy before generating production code.

​
Guardrails

  • Never expose SENDREALM_API_KEY, Firebase service account JSON, or APNs .p8 keys in browser or mobile code.
  • Distinguish Sendrealm development or production devices from iOS APNs sandbox or production.
  • Treat audience sends as queued and direct device/contact/user sends as immediate.
  • Do not promise device display. Provider accepted or sent counts are not proof that a notification appeared on the device.
  • Use diagnostics before changing backend targeting logic.
  • Use the MCP push_test_send tool only with one device selected from push_devices_list; broad push sends and campaign launch are intentionally unavailable through MCP.

​
Source Docs