Paths, shallow reads and queries. Changes wait for approval.
The screenshots show GateRook 2.0.0: the Firebase Realtime Database form, the endpoint selector, and this connector’s actual tool preview. The form and preview have not been saved. Select a screenshot to open it at full size.
1. Create a connection and enter the settings
In GateRook, open Connections, select Add connection, search for Firebase Realtime Database, choose its card and select Continue to configure.
Copy the Realtime Database URL from the Firebase console. It identifies one database, not the Firebase project’s general web address.
Prepare local Application Default Credentials or a service account key. Use an identity limited to the database operations you intend; this connector authenticates to the database REST API.
Enter a Name, for example firebase-rtdb-demo. Your AI app uses this name to choose the connection.
Enter Database URL, such as the console’s https://<database>.firebaseio.com or regional firebasedatabase.app address.
Limit Paths to the top-level branches the AI may use, such as public or orders. An empty list permits the whole database within the identity’s access.
Choose Existing Google sign-in (ADC) or Service account key (JSON) under Authentication. Optionally set Service account to impersonate with a read-only database role.
Choose Development, Staging or Production to match the service. Review the connector’s limit and access settings before continuing.
2. Test the connection and add it to an endpoint
Select Continue to test. GateRook checks the settings from your computer. Review the result and resolve any connection, certificate or permission error before continuing.
If access is denied, check the exact database URL and the signed-in identity’s database permissions. Refresh an expired Google sign-in when prompted; the permission and OAuth scopes of the credentials still apply.
After the test passes, select Continue to add to an endpoint. Choose the endpoint your AI app uses, review its tool modes, then select Save connection. GateRook offers default as the starter endpoint.
3. Use the connection from your AI IDE
After saving Firebase Realtime Database on the endpoint and passing its connection test, ask your AI app to use firebase-rtdb-demo, or the name you chose. If its tools are missing, confirm the endpoint assignment and refresh the MCP connection or start a new chat.
The preview below shows this connector’s default tools before saving. The table explains what each tool can do; connection settings, credentials and endpoint policies can restrict access further.
Start with a small read request. Replace example resource names with existing resources your connection may access. Open Activity after the call to inspect its connection, tool, arguments, policy decision and result metadata.
Ask your AI, for example
- “Read the public/status path on firebase-rtdb-demo.”
- “Using firebase-rtdb-demo, show at most five records under orders.”
- “Read orders/order-123 on firebase-rtdb-demo without changing it.”
| Tool | What it does | Starts as |
|---|---|---|
rtdb_get | The data at one path. At the root only the top-level keys, unless you ask otherwise; orderBy with limitToFirst, limitToLast, startAt, endAt or equalTo reads some children. An answer larger than the response size is refused: narrow it. | Read only |
rtdb_write | Sets, updates or deletes the data at one path. You approve the exact request. | Approval |
You can change each tool’s mode on the endpoint. Every call your AI makes appears in Activity.