Skip to main content
Glama
gemini-dk

Firebase MCP Server

by gemini-dk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Firebase MCP Server

No user-submitted related servers found.

    Related Servers

    • Firebase MCP

      gannonh
      A
      license
      Not graded
      quality
      D
      maintenance
      The Firebase MCP server provides a standardized interface to interact with Firebase services, including Firebase Authentication, Firestore, and Firebase Storage.
      873 npm
      248
      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.
      32 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
      33 npm
      MIT

    • Firestore Advanced MCP

      diez7lm
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables large language models like Claude to perform comprehensive interactions with Firebase Firestore databases, supporting full CRUD operations, complex queries, and advanced features like transactions and TTL management.
      6 npm
      4
      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

    A3.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools are organized by Firebase service (Authentication, Firestore, Storage) and specific operations within each service, making it easy to distinguish between them. For example, firestore_get_document retrieves a single document while firestore_list_documents lists multiple documents with filtering.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, with clear service prefixes (auth_, firestore_, storage_). All tools use snake_case consistently, and the naming convention is predictable and readable across all nine tools.

    Tool Count5/5

    With 9 tools, this server is well-scoped for covering core Firebase operations across multiple services. Each tool earns its place by addressing distinct functionality without being overwhelming. The count is appropriate for the server's purpose of providing access to Firebase Authentication, Firestore, and Storage.

    Completeness4/5

    The tool surface provides excellent coverage for Firestore (full CRUD operations plus listing) and good coverage for Storage and Authentication. Minor gaps exist, such as no user creation/update/deletion in Authentication and no file upload/download in Storage, but agents can work around these limitations for many common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources