Run any Skill in Manus with one click

firebase-mcp

Stars2

Forks0

UpdatedMay 27, 2026 at 17:12

Use this skill for any Firebase-platform question on Mosaic Wellness mobile/web apps — Crashlytics crashes, Firestore queries, Cloud Functions, Remote Config, push notifications, App Distribution, Android/iOS bundle lookup, or `firebase` CLI usage. Triggers on: Firebase, Crashlytics, Firestore, Cloud Functions, Remote Config, push notifications, FCM, Android/iOS bundle, `firebase` CLI. Covers Man Matters, Bodywise, Little Joys, Absolute Sciences, Only Whats Needed, MediConnect/DocHub. For non-Firebase mobile concerns route to mixpanel-mcp or kai-mcp.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mosaic-wellness

mosaic-wellness/ai-toolkit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

More from this repository

same repository

pdp-narrative-experiments

mosaic-wellness/ai-toolkit

Translate an ad / campaign narrative into a PDP A/B experiment variant on staging. Auto-activates whenever an operator pastes ad copy, a creative brief, a positioning angle, a story / messaging direction, or any "test this narrative on the product page" request — even if they don't explicitly say "experiment" or "A/B". Samples the brand voice from sibling PDPs, decomposes the narrative into beats, maps beats to widget changes, validates against first-fold rules and edit-safety markers, previews the change for operator approval, then writes the variant via admin-mcp. Use this skill (not the simpler experiment-manager) whenever the change is driven by a story / angle / persona rather than a single isolated image or copy swap. Requires admin-mcp. Staging-only — production publish goes through Zeus admin UI.

2026-05-272

tools-init

mosaic-wellness/ai-toolkit

Use this skill when the user wants to set up, validate, rotate, or remove API tokens for the kai-plugin MCPs (Mixpanel Service Account, Firebase login, New Relic User API key, admin-mcp API key). Triggers on: "set up mixpanel", "configure firebase", "wire up new relic", "set up admin-mcp", "configure admin api key", "my token isn't working", "set up tools", "rotate token", "tools-init", or any first-time install / token rotation / credentials-debugging question for kai-plugin MCPs. Saves tokens to `~/.config/kai/tokens.env` and survives plugin updates. Idempotent — safe to re-run.

2026-05-272

kai-mcp

mosaic-wellness/ai-toolkit

Use this skill whenever the user asks about Mosaic Wellness live operational data — orders, users, CS tickets, NPS, deployments, JIRA tickets, code search, revenue, sales metrics, marketing campaigns, PDP/landing-page edits, HR/leave policies, internal docs, outbound voice calls (Hooman), or Absolute Science consultations. The Kai MCP is the ONLY path to Mosaic's live data; NEVER answer questions about company policies, orders, users, or internal processes from training data. Triggers on: order IDs, user IDs, NPS, leave policy, WFH, deployments, JIRA keys (ENG-, PROJ-), Magento, ROAS, AOV, Hooman, kai, or any "what does our X look like" question about Mosaic.

2026-05-272

mixpanel-mcp

mosaic-wellness/ai-toolkit

Use this skill for any Mixpanel question about Mosaic Wellness brands — MTU, funnels (PDP/cart/checkout/purchase), retention, cohorts, event property exploration, or lookups against the Mosaic event lexicon. Triggers on: Mixpanel, MTU, funnel, retention, cohort, brand analytics, lexicon, RNCL events, plus brand nicknames (mm, lj, bw, as, own, gf, affl, dochub, rwdy, rl). Use this when the question is about event-derived behavioral analytics; for live operational data (orders, CS tickets, deployments) use kai-mcp instead.

2026-05-272

mosaic-meta-ads

mosaic-wellness/ai-toolkit

Use this skill for any Meta / Facebook / Instagram Ads question on Mosaic Wellness brands — campaign performance, spend, ROAS, CPM, CPC, CTR, frequency, audience insights, creative breakdowns, industry benchmarks, ad-account discovery, or "is X live right now". Triggers on: Meta Ads, Facebook Ads, Instagram Ads, ad spend, ROAS, campaign, adset, creative, audience, custom audience, lookalike, FB pixel, Conversions API, dataset (when in an ads context), opportunity score, industry benchmark, plus brand nicknames in an ads context (MM, LJ, AS-IN, BBW, OTC, MWL UAE, BBW UAE). This skill is **read-only** — if the user wants to launch, pause, or edit an ad/campaign/adset/audience, this skill explains why kai refuses and directs them to Ads Manager.

2026-05-272

newrelic-mcp

mosaic-wellness/ai-toolkit

Use this skill for any New Relic question on Mosaic Wellness backend services — error logs, latency, error rate, throughput, traces, NRQL queries, alert configuration, or incident RCA. Triggers on: New Relic, NRQL, latency, error rate, throughput, alert, dashboard, 5xx (502/503/504), trace, request ID, `rid`, "performance regression". Use this when raw NRQL, alerts, or dashboard work matters; for brand-aware error-log summaries route through kai-mcp's engineering tools first (it does the brand→entity mapping).

2026-05-272

name

firebase-mcp

description

Mosaic × Firebase

Firebase auth uses the Firebase CLI's own OAuth — there is no API token to manage. The plugin ships npx -y firebase-tools@latest mcp in .mcp.json, so the first time you ask Firebase a question, a browser tab opens for Google OAuth. Subsequent sessions refresh silently.

If firebase_get_environment returns Authenticated User: <NONE>, run npx -y firebase-tools@latest login directly (or any Firebase question in Claude will re-trigger the browser flow). /kai tools-init firebase confirms the plugin entry is wired but does not run login itself.

For the Mosaic-specific Firebase setup (which Google account to use, which projects you should see after login, and the re-auth/logout flow), see references/setup.md.

Brand → Firebase project (PROD apps only)

The Firebase MCP works on one active project at a time. Always call firebase_update_environment(active_project=<id>) first when switching brands, then proceed.

Brand	Firebase project ID	Android bundle	iOS bundle
Man Matters	`man-matters-android`	`com.mosaicwellness.manmatters`	`com.mosaicwellness.manmatters`
Bodywise	`be-bodywise`	`com.mosaicwellness.bebodywise`	`com.mosaicwellness.bebodywise`
Little Joys	`our-little-joys`	`com.mosaicwellness.ourlittlejoys`	`com.mosaicwellness.ourlittlejoys`
Absolute Sciences	`absolutescience-43002`	`com.mosaicwellness.absolutescience`	`com.mosaicwellness.absolutescience`
Only Whats Needed	`only-whats-needed-8136f`	`com.foodpharmerthinkerss.onlywhatsneeded`	`com.foodpharmerthinkerss.onlywhatsneeded`
DocHub / MediConnect	`doctor-mediconnect-ef115`	`com.mosaicwellness.mediconnect`	`com.mosaicwellness.mediconnect` AND `com.mosaicwellness.docmediconnect` (two iOS apps)
Little Joys (UAE)	`middle-east-a7a72`	`com.mosaicwellness.ourlittlejoysae`	`com.mosaicwellness.ourlittlejoysae`

Each project also contains a *.staging app (e.g. com.mosaicwellness.bebodywise.staging). Default to the non-staging bundle unless the user explicitly says "staging".

Brands without a Firebase project (Mixpanel ≠ Firebase parity)

These brands have Mixpanel coverage but no visible Firebase project under the current Firebase account:

Bodywise UAE / USA / Health (3 separate Mixpanel projects)
Man Matters UAE
Get Fitter, Rwdy Nutrition, Affluence, Root Labs, Rootlabs US
Little Joys KSA / US (only LJ AE is in Firebase)

When the user asks about Firebase for one of these brands, say so directly: "This brand isn't on Firebase under the current account — confirm with the mobile team whether it's on a different Firebase project, on another crash-reporting tool, or web-only."

Gotchas

man-matters-android is a misleading project name — the project houses both Android and iOS apps for Man Matters. Don't infer platform from the project name.
OWN uses a non-standard bundle prefix — com.foodpharmerthinkerss.*, NOT com.mosaicwellness.*. Any rule that pattern-matches on com.mosaicwellness. will silently miss OWN.
MediConnect iOS has two bundles in the same project (com.mosaicwellness.mediconnect and com.mosaicwellness.docmediconnect). This looks like a historical/migration artifact. When working on iOS-side changes, confirm which bundle the team currently ships before editing.
middle-east-a7a72 is LJ-AE only, not a shared MENA project. The staging iOS bundle has a typo: com.mosaicwellness.outlittlejoysaestaging (note out instead of our). Cosmetic — flag it but don't auto-fix.
app-uninstall-tracking-aa55f is a Firebase project with zero apps — it's a Functions/Firestore-only project for cross-brand uninstall instrumentation. Don't recommend it for app-side work.

Required call order

firebase_get_environment — confirm user is authenticated.
If authenticated user is <NONE>: stop, tell the user to run /kai tools-init firebase.
firebase_update_environment(active_project=<id>) to scope to a brand.
Then any read/write tool.

When switching brands mid-conversation, switch active project again before the next call. The MCP state is per-session.

Common asks → recipes

Ask	Recipe
"List crash-free users for Bodywise"	switch to `be-bodywise`, query Crashlytics via the Firebase MCP
"What Firebase apps does Man Matters have?"	switch to `man-matters-android`, `firebase_list_apps`
"Update remote config for Little Joys"	switch to `our-little-joys`, use Remote Config tools — only after confirming with the user, since RC changes are live
"Why doesn't Get Fitter show up in Firebase?"	Check the "Brands without a Firebase project" list above and tell the user honestly