Introduction

Push notifications for any app

Native Notify sends push notifications to your users and to individuals — with inboxes, analytics, scheduling and an AI agent that can set the whole thing up for you. Everything is managed from one dashboard, a simple API, or your own AI agent through the MCP server.

• Any framework. Flutter, bare React Native, native Swift or Kotlin, .NET, Unity, Expo, or the web — your app registers its own APNs/FCM device tokens and Native Notify delivers through Apple's and Google's push services. Universal Push (Any Framework) leads these docs; no SDK required.
• Set up by an agent. Agent Notify reads your project — with or without GitHub — and wires push notifications in for you, answering with exact copy-paste code and the precise file and place to change. See Agent Notify Without GitHub.
• Any audience. Send to every device, to individual subscribers, to keyed groups, or to topic subscribers.
• Inboxes. A prebuilt notification inbox for React Native apps, and a bell + inbox widget for web sites.
• Scheduling & segments. Schedule one-off or recurring sends (quiet hours included) and target named segments of subscribers.
• Analytics. Active users and growth, screen usage, retention, session activity, and how many of your push notifications get opened.

Using the Expo SDK? The native-notify package path is fully documented in Expo Push (Classic) at the end of the sidebar.

Built for AI agents

The future of push notifications is AI agents doing the sending for you. Native Notify ships a hosted MCP server so agents (Claude, Cursor, ChatGPT agents, or your own) can run your account end-to-end with one access token: send and schedule notifications, manage apps and subscribers, and read your analytics — while always working from the current documentation instead of stale training data.

Join our Community

If you have questions about anything related to Native Notify, you're always welcome to ask our community on GitHub or check out our tutorial videos on YouTube.