> ## Documentation Index
> Fetch the complete documentation index at: https://www.truefoundry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up Firebase Crashlytics MCP Server

> Create a GCP service account and connect Firebase Crashlytics crash data tools to TrueFoundry.

A Firebase Crashlytics MCP server lets agents inspect crash issues, stack traces, crash events, and reports. It typically authenticates with a Google Cloud service account JSON key.

## Prerequisites

* A TrueFoundry account with permission to add MCP servers.
* A Firebase project with Crashlytics enabled.
* Permission to create service accounts in the backing Google Cloud project.

## Create a Service Account

In Google Cloud Console, select the project that backs your Firebase project and create a service account named `crashlytics-mcp`. Grant:

| Role                               | Purpose                                            |
| ---------------------------------- | -------------------------------------------------- |
| `roles/firebase.viewer`            | Read Firebase project metadata                     |
| `roles/firebasecrashlytics.viewer` | Read Crashlytics data                              |
| `roles/firebasecrashlytics.user`   | Optional, only if tools need to update issue state |

Create a JSON key and store it securely.

## Register in TrueFoundry

Deploy the Firebase Crashlytics MCP server as a remote service or hosted stdio server. Configure the service account JSON and Firebase project ID as environment variables or secret-backed configuration expected by your MCP server implementation.

Add the resulting MCP server in **MCP Gateway** and add collaborators. Confirm that tools are visible in the **Tools** section, then try them from the **Agent Playground**.

## Security Notes

Treat the service account JSON as a password. Use Viewer roles unless agents must modify issue state. Revoke access by deleting the service account key in Google Cloud Console.