Antigravity Ai Directory Firebase Mcp

Created By
6 months ago
Build apps with Firebase Authentication, Firestore, Storage, and more. Real-time synchronization and serverless backend.
Overview

What is Antigravity AI Directory - Firebase MCP?

Antigravity AI Directory - Firebase MCP is a platform that allows developers to build applications using Firebase services such as Authentication, Firestore, and Storage, providing real-time synchronization and a serverless backend.

How to use Antigravity AI Directory - Firebase MCP?

To use this platform, create a Firebase project, generate a service account key, download the JSON key file, and add the credentials to your configuration.

Key features of Antigravity AI Directory - Firebase MCP?

  • Real-time database capabilities
  • Serverless architecture
  • Easy integration with Firebase services

Use cases of Antigravity AI Directory - Firebase MCP?

  1. Building web and mobile applications with real-time data updates.
  2. Implementing user authentication and data storage solutions.
  3. Creating scalable applications without managing server infrastructure.

FAQ from Antigravity AI Directory - Firebase MCP?

  • What services does Firebase MCP support?

Firebase MCP supports various Firebase services including Authentication, Firestore, and Storage.

  • Is there a cost associated with using Firebase MCP?

Firebase MCP is free to use, but Firebase services may have associated costs based on usage.

Server Config

{
  "mcpServers": {
    "firebase": {
      "env": {
        "FIREBASE_PROJECT_ID": "your_project_id",
        "FIREBASE_PRIVATE_KEY": "your_service_account_key"
      },
      "args": [
        "-y",
        "@firebase/mcp-server"
      ],
      "command": "npx"
    }
  }
}
Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
-
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago