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 MCP Integration for Codex

Connect Firebase to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write Manual OAuth token auth

Submit Firebase feedback View package source

Connect Firebase to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Firebase MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

{
  "mcpServers": {
    "kosmokrator-firebase": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=firebase",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=firebase --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Firebase instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Firebase Tools Visible to Codex

Codex sees stable MCP tool names generated from the Firebase integration catalog.

MCP tool	Source function	Type	Description
`integration__firebase__firebase_list_projects`	`firebase.firebase_list_projects`	Read	List all Firebase projects the caller has access to. Returns project display names and IDs.
`integration__firebase__firebase_get_project`	`firebase.firebase_get_project`	Read	Get details of a specific Firebase project by its resource name.
`integration__firebase__firebase_list_databases`	`firebase.firebase_list_databases`	Read	List Cloud Firestore databases in a Firebase project.
`integration__firebase__firebase_list_documents`	`firebase.firebase_list_documents`	Read	List documents in a Firestore collection.
`integration__firebase__firebase_list_collections`	`firebase.firebase_list_collections`	Read	List collection IDs under a Firestore document or database root.
`integration__firebase__firebase_list_users`	`firebase.firebase_list_users`	Read	List users in a Firebase project via the Identity Toolkit API.
`integration__firebase__firebase_get_current_user`	`firebase.firebase_get_current_user`	Read	Get the currently authenticated OAuth2 user profile information.

Related Firebase Pages

Firebase CLIUse direct JSON commands instead of MCP discovery. Firebase MCPFull gateway reference and MCP tool names. KosmoKrator for CodexClient-level gateway setup.