Firebase

@firebase look up what sign-in methods are enabled for user@example.com in our project

The Firebase account for user@example.com has previously signed in using: password (email/password provider) and google.com (Google Sign-In). Note that if anti-enumeration protection is enabled in your Firebase project settings, this list may be empty even when the account exists. An empty result does not confirm the account is unregistered.

This example shows account discovery, useful for debugging sign-in flows or building custom UIs. Be aware that Firebase anti-enumeration settings can suppress results to prevent account enumeration attacks, so an empty list is not proof an account doesn't exist. Requires a valid Web API key with Authentication enabled.

@firebase sign in testuser@company.com with password 'temp123' and give me fresh tokens

Successfully signed in testuser@company.com. Returned a fresh ID token (expires in 1 hour) and a refresh token for session persistence. The ID token can be used to authenticate backend requests. The user's Firebase UID is aB3dEf9GhI2jK. Email/Password provider must be enabled in your Firebase project for this to work.

This demonstrates password-based authentication, the most common Firebase sign-in method. The MCP returns tokens but does not store them—your application must handle token storage and refresh logic. Requires the Email/Password provider to be enabled in Firebase Console and a valid API key. Failed attempts count toward rate limits.

@firebase get our project's auth config and list which domains are authorized for OAuth redirects

Firebase project ID: my-app-prod-f8a2c. Authorized domains for OAuth redirects: my-app.com, my-app.firebaseapp.com, localhost. This configuration is public and does not require user authentication—it's the same data the Firebase SDK fetches on initialization. The project has Email/Password, Google, and Anonymous providers enabled.

This read-only example retrieves public project metadata, useful for verifying environment setup or debugging redirect issues in OAuth flows. No user authentication is needed—only a valid Web API key. This does not expose private project settings or backend access; it returns the same data visible to any client initializing the Firebase SDK.

When Firebase MCP helps support debug sign-in failures

A 6-person SaaS team fields 15-20 weekly tickets about users locked out of their accounts. The Firebase MCP gives support reps a read-only way to check which sign-in methods a customer email has used, verify password-reset codes, and confirm project config without touching production Firebase Console credentials. The Discover Sign-In Methods tool surfaces whether a user tried Google OAuth versus email/password, cutting median ticket resolution from 45 minutes to under 10. This works when your support team is small enough that sharing one API key is acceptable and Firebase anti-enumeration settings allow method discovery. If you need audit trails per rep or handle PII under strict compliance, you want a custom support dashboard with role-based Firebase Admin SDK access instead. For teams under 10 people triaging auth issues daily, the MCP is the fastest path to first-line diagnosis.

Firebase MCP speeds up staging account creation in test cycles

A 4-person product team runs weekly QA sprints where testers need fresh Firebase accounts with different auth providers to validate onboarding flows. The Sign In With Custom Token and Sign In With Identity Provider tools let a QA engineer script account creation from a CI pipeline or Switchy chat command, rotating test users without manual Firebase Console clicks. The MCP's token-refresh capability keeps long-running Playwright sessions authenticated across multi-hour test suites. This setup shines when you run 5-10 QA cycles per month and your test matrix covers email/password, Google, and one other provider. If your test matrix includes 6+ identity providers or you need per-tester Firebase projects, the 8-tool scope gets narrow and you should build a dedicated test-account service with the Admin SDK. For small teams doing weekly regression on 2-3 auth flows, the MCP cuts QA setup time in half.

When Firebase MCP clarifies drop-off in sign-up funnels

A 3-person growth team sees 40% of new users abandon sign-up between entering their email and completing authentication. The Firebase MCP's Get Auth Project Config and Verify Password Reset Code tools let the team confirm that authorized domains match the production URL and that password-reset emails are landing with valid OOB codes. The Sign In With Email Link tool reproduces the exact user flow in a Switchy session, surfacing whether the issue is token expiration, misconfigured deep links, or email client stripping query params. This diagnostic path works when your sign-up volume is under 500 weekly attempts and you can reproduce the failure in under 10 minutes. Above 2,000 weekly sign-ups or when drop-off spans multiple sessions, you need Firebase Analytics event tracking and a proper funnel dashboard. For early-stage teams debugging a specific onboarding regression, the MCP gives you the answer in one 15-minute investigation instead of a day of log spelunking.