Firebase for AI agents

Firebase Authentication handles sign-in and sign-up flows for apps, including password, email link, and identity provider logins, used by developers building user accounts into mobile and web apps. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Security and identityAPI keyMCP + RESTfirebase.google.com
AUDIT LOG · FIREBASEPOLICY: acme-support
09:41:07 · claude · u_8f2read
firebase.get_auth_project_config
Get Auth Project Config✓ allowed · 212ms
09:41:09 · claude · u_8f2write
firebase.refresh_id_token
Refresh ID Token✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
firebase.verify_password_reset_code
Verify Password Reset Code✕ blocked · policy: deny
EVERY FIREBASE CALL, ON THE RECORD
01 · USE CASES

What agents do in Firebase.

01

Check available sign-in methods

Discover which sign-in methods are enabled for an email before directing a user to the right flow.

02

Refresh a user's session token

Refresh an ID token so a user's session stays active without asking them to log in again.

03

Approve before a password reset

Require confirmation before verifying a password reset code, since it can hand over account access.

02 · ACTIONS

8 Firebase actions, graded by risk.

Every Firebase action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

1

Look things up. Allowed by default.

  • firebase.get_auth_project_config
    Get Auth Project Config

write

6

Create and change things. Allow, or ask the user first.

  • firebase.refresh_id_token
    Refresh ID Token
  • firebase.sign_in_with_idp
    Sign In With Identity Provider
  • firebase.sign_in_with_password
    Sign In With Password
  • firebase.sign_in_with_email_link
    Sign In With Email Link
  • firebase.discover_sign_in_methods
    Discover Sign-In Methods
  • firebase.sign_in_with_custom_token
    Sign In With Custom Token

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • firebase.verify_password_reset_code
    Verify Password Reset Code
03 · HOW IT WORKS

Firebase in three steps.

  1. 01Your users connect FirebaseThey add their Firebase api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “refresh ID Token” can wait for the user, and “verify Password Reset Code” can be denied outright.
  3. 03Any agent can actYour agent calls Firebase through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('firebase', {
  read: 'allow',
  write: 'ask',        // refresh_id_token
  destructive: 'deny',  // verify_password_reset_code
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Firebase connects.

Users add their Firebase api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Firebase connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Firebase from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Firebase and Arc0, answered.

Q01

Can I use Firebase with Claude, ChatGPT or Cursor?

Yes. Connect Firebase to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Firebase actions you allow.

Q02

How do users connect Firebase?

Users add their Firebase api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Firebase actions can my agent take?

8 in total: 1 read, 6 write and 1 destructive, such as “refresh ID Token”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Firebase?

Yes. Actions like “verify Password Reset Code” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Firebase too?

Yes. The same Firebase connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Firebase into your agent.

Your users connect Firebase once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan