---
title: "pushengage"
description: "Integrate and debug the PushEngage push-notification SDK across iOS, Android, Flutter, and React Native."
canonical: https://agentpluginsdirectory.com/plugins/pushengage
last-updated: 2026-09-26
---

# pushengage
Integrate and debug the PushEngage push-notification SDK across iOS, Android, Flutter, and React Native.
- Slug: pushengage
- Publisher: PushEngage
- Repository: https://github.com/awesomemotive/pushengage-skills
- Manifest: plugin.json
- Version: 1.0.0
- License: MIT
- Category (editorial): integrations
- Skills: 6 (pushengage-android, pushengage-debug, pushengage-flutter, pushengage-ios, pushengage-react-native, pushengage)
- MCP servers: 1 (pushengage)
- Stars: 3
- Repository created: 2026-08-10
- Repository last pushed: 2026-08-11
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/pushengage
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What pushengage does, in the publisher's words

Helps an AI coding agent integrate and debug the PushEngage push-notification SDK across iOS, Android, Flutter, and React Native.

The six skills follow the open Agent Skills (SKILL.md) standard, so they work with any agent that supports it, Claude Code, Cowork, and other SKILL.md-compatible agents: while also shipping as an installable Claude Code plugin.

- A PushEngage account with an app configured in the dashboard.
- An AI coding agent that supports Agent Skills (Claude Code recommended).

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/awesomemotive/pushengage-skills/HEAD/README.md

## Skills

- pushengage-android: Use ONLY when the active repo is a native Android app (build.gradle or build.gradle.kts at root with AndroidManifest.xml under app/src/main) AND there is NO `pubspec.yaml` with a `flutter:` SDK block AND NO `package.json` with `react-native` or `expo` dependency. Handles full PushEngage integration…
- pushengage-debug: Use when invoked by a PushEngage platform spoke (pushengage-ios, etc.) to diagnose a broken integration. Runs a static audit, matches against a version-pinned known-issues table, then falls back to a symptom-driven decision tree. Not invoked directly by customers.
- pushengage-flutter: Use ONLY when the active repo is a Flutter app (`pubspec.yaml` with a `flutter:` SDK block). Handles full PushEngage integration end-to-end (Dart init + Android native config + iOS native config + NSE) plus debugging existing integrations. Do not use for native iOS, native Android, or React Native…
- pushengage-ios: Use ONLY when the active repo is a native iOS app (Podfile, Package.swift, or *.xcodeproj present at the project root) AND there is NO `pubspec.yaml` with a `flutter:` SDK block AND NO `package.json` with `react-native` or `expo` dependency. Handles full PushEngage integration end-to-end, plus debu…
- pushengage-react-native: Use ONLY when the active repo is a React Native app (`package.json` with `react-native` dep, typically alongside `ios/` and `android/` folders, Turbo Modules / New Architecture). Handles full PushEngage integration end-to-end (JS init + Android native config + iOS native config + NSE) plus debuggin…
- pushengage: Use when integrating, debugging, asking about, or auditing PushEngage push notifications in any mobile app (iOS, Android, Flutter, React Native). Detects the customer's platform and hands off to the matching platform spoke.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- pushengage: transport: stdio; command: npx -y @pushengage/mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.