home / mcp / firebase app distribution api mcp server

Firebase App Distribution API MCP Server

MCP Server generated by mcp.ag2.ai

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "ag2-mcp-servers-firebase-app-distribution-api": {
      "command": "python",
      "args": [
        "mcp_server/main.py",
        "stdio"
      ],
      "env": {
        "CONFIG": "A JSON string containing the configuration",
        "SECURITY": "Environment variables for security parameters (e.g., API keys)",
        "CONFIG_PATH": "Path to a JSON configuration file (e.g., mcp_server/mcp_config.json)"
      }
    }
  }
}

You run an MCP (Model Context Protocol) server to expose a specific API as a scalable, protocol-friendly service. This server enables MCP clients to interact with the Firebase App Distribution API through a structured, model-driven interface.

How to use

To use this MCP server, start it in stdio mode and connect your MCP client to the runtime. The server exposes the Firebase App Distribution API via the MCP interface, allowing you to send requests and receive model-context responses in a consistent, testable way.

How to install

Prerequisites for running this MCP server are Python 3.9 or later, and pip with uv available.

# Install Python dependencies (from within your project directory)
pip install -e ".[dev]"

# Alternatively, use uv to install editable dev dependencies
uv pip install --editable ".[dev]"

Additional setup and usage notes

You run the MCP server using the main script in stdio mode. The runtime command is explicitly shown here so you can start the server straightforwardly.

# Start the MCP server in stdio mode
python mcp_server/main.py stdio

Configuration and environment

You can configure the server at startup using environment variables. The following are available in this setup:

- CONFIG_PATH: Path to a JSON configuration file (for example, mcp_server/mcp_config.json).

- CONFIG: A JSON string containing the configuration.

- SECURITY: Environment variables for security parameters (for example, API keys).

Note: These variables are recognized by the server at startup, and the exact loading behavior can be found in the main entry point logic.