How to connect Firebase to OpenClaw
Connect Firebase to OpenClaw with ClawLink: paste your Firebase key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
FirebaseAPI KEYMCPFirebase Authentication client tools for project discovery, user sign-in and sign-up flows, out-of-band codes, and Secure Token refresh using a Firebase Web API Key.. Once connected, OpenClaw can read and act on Firebase from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Firebase access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Firebase setup: install one ClawHub skill, connect Firebase in the browser, and OpenClaw can call real Firebase actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Firebase.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Firebase
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Firebase?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Firebase in the ClawLink dashboard — paste your Firebase API key once.
Verify the connection by asking OpenClaw:
Use Firebase to discover sign in methods and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Firebase is connected in the dashboard, that agent calls the same 8 Firebase tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Firebase MCP for OpenClaw
Looking for a Firebase MCP server for OpenClaw? ClawLink connects Firebase to OpenClaw and exposes 8 Firebase tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Firebase integration works the same way.
What the OpenClaw Firebase integration can do
8 Firebase tools are ready for OpenClaw once the account is connected.
All 8 Firebase tools for OpenClaw
| Tool | What it does |
|---|---|
Discover sign in methods firebase_discover_sign_in_methods | Look up sign-in methods previously used by a Firebase account email |
Get auth project config firebase_get_auth_project_config | Get the public Firebase Authentication configuration associated with the connected Web API key |
Verify password reset code firebase_verify_password_reset_code | Validate a Firebase password-reset OOB code and identify the associated email and request type |
Refresh ID token firebase_refresh_id_token | Exchange a Firebase refresh token for a fresh Firebase ID token and rotated refresh token using |
Sign in with custom token firebase_sign_in_with_custom_token | Exchange a trusted server-minted Firebase custom token for a Firebase ID token and refresh token |
Sign in with email link firebase_sign_in_with_email_link | Complete Firebase email-link sign-in using an email address and the one-time OOB code from a |
Sign in with idp firebase_sign_in_with_idp | Sign in with one configured external identity provider using provider-specific OAuth or OIDC |
Sign in with password firebase_sign_in_with_password | Sign in an existing Firebase Authentication user with email and password and return fresh ID |
Try it: find the Firebase tool you need
Browse the 8 Firebase tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Firebase to discover sign in methods and walk me through the result in plain English.
Pull the relevant data from Firebase, summarize it in plain English, and point out anything that needs attention.
Use Firebase to verify password reset code and walk me through the result in plain English.
Use Firebase to refresh id token and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Firebase working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Firebase API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Firebase account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Firebase. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Firebase actions to the runtime in a format your agent can reliably use. | 8 tools for Firebase are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Firebase to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Firebase in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Firebase key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Firebase skill but can't call the tools
The ClawHub skill teaches OpenClaw about Firebase, but the calls run through the ClawLink plugin and your connected account. Make sure Firebase is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Firebase from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Firebase tools
Firebase tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Firebase call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Firebase returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Firebase has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Firebase integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Firebase: link your Firebase account once in the browser and OpenClaw can call the Firebase API through 8 ready-made tools — no custom code or token handling.
How do I add Firebase to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Firebase skill from ClawHub, then you click Connect in the dashboard to authorize Firebase. OpenClaw calls the tools from the next message — no config files, and the Firebase key you paste is stored server-side instead of in your environment.
How long does it take to connect Firebase to OpenClaw?
About two minutes. Sign in, click Connect next to Firebase in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Firebase up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Firebase working from chat.
OpenClaw installed the Firebase skill but can't call the tools
The ClawHub skill teaches OpenClaw about Firebase, but the calls run through the ClawLink plugin and your connected account. Make sure Firebase is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw GitHub integration
Manage repositories, issues, pull requests, and workflows
Connect PagerDuty
Manage incidents, on-call schedules, and services
Connect SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.