Can I use Firebase as a CLI?

Yes. KosmoKrator exposes a Firebase CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Firebase through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Firebase tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Firebase credentials stored?

Firebase credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Firebase MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

other

Firebase CLI for Cron Jobs

Use the Firebase CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write Manual OAuth token auth

Submit Firebase feedback View package source

Firebase CLI for Cron Jobs

Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.

Use the headless CLI from cron when an operation should run without an interactive agent session. The Firebase CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Firebase CLI for Cron Jobs
kosmokrator integrations:configure firebase --set access_token="$FIREBASE_ACCESS_TOKEN" --set project_id="$FIREBASE_PROJECT_ID" --enable --read allow --write ask --json
kosmo integrations:call firebase.firebase_list_projects '{"page_size":1,"page_token":"example_page_token"}' --json

Discovery Before Execution

Agents and scripts can inspect Firebase docs and schemas before choosing a function.

kosmo integrations:docs firebase --json
kosmo integrations:docs firebase.firebase_list_projects --json
kosmo integrations:schema firebase.firebase_list_projects --json
kosmo integrations:search "Firebase" --json
kosmo integrations:list --json

Useful Firebase CLI Functions

Function	Type	Parameters	Description
`firebase.firebase_list_projects`	Read	page_size, page_token	List all Firebase projects the caller has access to. Returns project display names and IDs.
`firebase.firebase_get_project`	Read	name	Get details of a specific Firebase project by its resource name.
`firebase.firebase_list_databases`	Read	parent	List Cloud Firestore databases in a Firebase project.
`firebase.firebase_list_documents`	Read	parent, collection_id, page_size, page_token, order_by	List documents in a Firestore collection.
`firebase.firebase_list_collections`	Read	parent, page_size, page_token	List collection IDs under a Firestore document or database root.
`firebase.firebase_list_users`	Read	max_results, page_token	List users in a Firebase project via the Identity Toolkit API.
`firebase.firebase_get_current_user`	Read	none	Get the currently authenticated OAuth2 user profile information.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Firebase CLI Pages

CI Firebase CLI for CI. Shell Scripts Firebase CLI for shell scripts. Headless Automation Firebase CLI for headless automation. Coding Agents Firebase CLI for coding agents.