Firebase Crashlytics MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BIGQUERY_DATASET_ID | No | BigQuery dataset ID for Crashlytics | firebase_crashlytics |
| BIGQUERY_PROJECT_ID | Yes | Your Firebase project ID | |
| DEFAULT_CRASH_LIMIT | No | Default limit for crash queries | 10 |
| GOOGLE_SERVICE_ACCOUNT_KEY | Yes | Path to Google Cloud service account JSON file, or base64-encoded content |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_available_appsB | List all available apps in the Firebase Crashlytics dataset |
| get_fatal_crashesB | Get fatal crashes for a specific app package name |
| get_anr_issuesB | Get ANR (Application Not Responding) issues for a specific app package name |
| get_crash_detailsC | Get detailed information for a specific crash |
| analyze_crash_trendsC | Analyze crash trends and statistics over time |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct aspect of crash analysis: apps, trends, fatal crashes, ANR issues, and crash details. No functional overlap.
All five tools follow a consistent verb_noun pattern in snake_case (e.g., list_available_apps, get_fatal_crashes), making naming predictable and clear.
Five tools is a reasonable size for a focused Crashlytics server, covering core read operations without being too bare or excessive.
The set covers trends, fatal crashes, ANR issues, and crash details but lacks non-fatal crashes and any mutation capabilities, which are notable gaps for a crash analysis server.