Skip to main content
Glama
LaishGlenberg

Firebase Emulator MCP Server

by LaishGlenberg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Firebase Emulator MCP Server

No user-submitted related servers found.

    Related Servers

    • Firebase MCP Server

      NigelThorne
      A
      license
      B
      quality
      D
      maintenance
      Enables inspection and querying of Firestore data and Cloud Function logs within the Firebase Emulator environment. It provides tools to navigate collections, retrieve documents, and filter function logs using regex and other criteria.
      9
      310 npm
      MIT

    • firebase-mcp

      s-h-u-h-a-r-i
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that exposes Firebase Firestore and Authentication to AI agents, supporting multi-project configurations and read operations.
      5
      26 npm
      MIT
    • Firebase MCP Server by firebase

      Firebase MCP Serverofficial

      firebase
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables interaction with Firebase projects and services, including deployment, database management, authentication, and local emulation, through natural language.
      2,186,911 npm
      4,467
      MIT

    • Firebase MCP Server

      dasasian
      A
      license
      Not graded
      quality
      A
      maintenance
      A general-purpose MCP server for Firebase that enables natural language interaction with Firestore, Auth, Storage, and Cloud Functions logs through schema-driven validation and context-efficient tools.
      29 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clear, distinct resource and action: Firestore operations are separate (list collections, query, get document), RTDB has a single get, Auth has list and get, and status/logs are emulator-wide. No two tools overlap in purpose.

    Naming Consistency4/5

    Most tools follow a consistent {service}_{action} pattern (firestore_list_collections, firestore_get, auth_list_users), but emulator_status and emulator_logs deviate to a noun-based pattern. Still predictable and easy to navigate.

    Tool Count5/5

    Eight tools is well-scoped for a Firebase emulator server, covering the core services (Firestore, RTDB, Auth) plus status and logs without unnecessary bloat.

    Completeness2/5

    The tool surface is heavily read-only: Firestore only supports list, query, and get, with no create, update, or delete operations. RTDB and Auth similarly lack write operations, making it impossible to fully manage data in the emulator.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources