Firebase Crashlytics MCP Server
Integrates with Firebase Crashlytics to retrieve fatal crashes, ANR issues, and app lists from BigQuery export data for AI-powered crash analysis.
Uses Google Cloud BigQuery to query Crashlytics data, requiring a service account with BigQuery Data Viewer and Job User roles.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Firebase Crashlytics MCP Server Show the latest 5 fatal crashes for com.example.app"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🔥 Firebase Crashlytics MCP Server
A clean, simple Model Context Protocol (MCP) server that integrates Firebase Crashlytics with BigQuery for AI-powered crash analysis. Built for use with Claude Code and other MCP-compatible AI assistants.
✨ Features
🔍 Simple Tools: Clean, single-responsibility tools for crash analysis
📱 App Discovery: Automatically discover all apps in your Firebase project
💥 Fatal Crash Analysis: Get detailed fatal crashes with stack traces
🐛 ANR Issue Detection: Analyze Application Not Responding issues
🔧 Easy Setup: Simple configuration with environment variables
🤖 AI-Optimized: Structured output perfect for AI analysis and debugging
Related MCP server: Google Tasks MCP Server
🚀 Quick Start
Prerequisites
Node.js 18+
Firebase project with Crashlytics enabled
BigQuery export enabled for Crashlytics
Google Cloud service account with BigQuery access
Installation
Clone the repository:
git clone https://github.com/your-username/mcp-crashlytics-server.git
cd mcp-crashlytics-serverInstall dependencies:
npm installBuild the project:
npm run buildConfiguration
Create environment file:
cp .env.example .envConfigure your environment variables:
# Google Cloud Service Account (choose one method)
GOOGLE_SERVICE_ACCOUNT_KEY=/path/to/your-service-account.json
# OR base64-encoded: GOOGLE_SERVICE_ACCOUNT_KEY=eyJhbGciOiJIUzI1...
# Your Firebase project settings
BIGQUERY_PROJECT_ID=your-firebase-project-id
BIGQUERY_DATASET_ID=firebase_crashlytics
# Optional: Default limit for crash queries
DEFAULT_CRASH_LIMIT=10Setup Firebase & BigQuery
Enable Crashlytics BigQuery Export:
Go to Firebase Console → Project Settings → Integrations
Enable BigQuery integration for Crashlytics
Data will be exported to
firebase_crashlyticsdataset
Create Service Account:
Go to Google Cloud Console
Navigate to IAM & Admin → Service Accounts
Create service account with these roles:
BigQuery Data ViewerBigQuery Job User
Download JSON key file
Register with AI Agents
Claude Code
# Register the MCP server
claude mcp add crashlytics -- node /path/to/mcp-crashlytics-server/dist/index.js
# Verify it's working
claude mcp listCursor
Add to your .cursorrules or cursor settings:
{
"mcpServers": {
"crashlytics": {
"command": "node",
"args": ["/path/to/mcp-crashlytics-server/dist/index.js"],
"env": {
"GOOGLE_SERVICE_ACCOUNT_KEY": "/path/to/your-service-account.json",
"BIGQUERY_PROJECT_ID": "your-firebase-project-id",
"BIGQUERY_DATASET_ID": "firebase_crashlytics"
}
}
}
}Windsurf
Add to your Windsurf settings or .windsurfrules:
{
"mcp": {
"servers": {
"crashlytics": {
"command": "node",
"args": ["/path/to/mcp-crashlytics-server/dist/index.js"],
"env": {
"GOOGLE_SERVICE_ACCOUNT_KEY": "/path/to/your-service-account.json",
"BIGQUERY_PROJECT_ID": "your-firebase-project-id",
"BIGQUERY_DATASET_ID": "firebase_crashlytics"
}
}
}
}
}Other MCP-Compatible IDEs
For other MCP-compatible tools, add this server configuration:
Command:
nodeArgs:
["/path/to/mcp-crashlytics-server/dist/index.js"]Environment Variables: Same as above (.env file values)
🛠️ Available Tools
1. list_available_apps
Discover all apps in your Firebase Crashlytics dataset.
Parameters: None
Returns: List of apps with crash counts
// Usage in Claude Code/Cursor
"What apps are available in my crashlytics data?"2. get_fatal_crashes
Get fatal crashes for a specific app.
Parameters:
app_package(required): App package name (e.g., "com.example.myapp")limit(optional): Number of crashes (1-50, default: 10)
// Usage in Claude Code/Cursor
"Get the 10 most recent fatal crashes for com.example.myapp"3. get_anr_issues
Get ANR (Application Not Responding) issues for a specific app.
Parameters:
app_package(required): App package namelimit(optional): Number of issues (1-50, default: 10)
// Usage in Claude Code/Cursor
"Show me ANR issues for com.example.myapp, limit to 5"📋 Example Usage
Once set up, you can ask Claude Code natural questions like:
# Discover your apps
"What apps do I have crash data for?"
# Get fatal crashes
"Show me the latest fatal crashes for my Android app"
"Get 5 fatal crashes for com.mycompany.myapp"
# Analyze ANR issues
"What ANR issues does my app have?"
"Show ANR problems for com.mycompany.myapp from the last week"🏗️ Project Structure
mcp-crashlytics-server/
├── src/
│ ├── index.ts # Main MCP server
│ ├── bigquery-client.ts # BigQuery integration
│ ├── crash-processor.ts # Crash data processing
│ ├── impact-analyzer.ts # Impact analysis
│ └── types.ts # TypeScript definitions
├── dist/ # Built JavaScript files
├── package.json
├── tsconfig.json
├── .env.example # Environment template
└── README.md🔧 Development
Running in Development Mode
npm run devBuilding
npm run buildLinting
npm run lintTesting
npm test🐛 Troubleshooting
Common Issues
1. "No MCP servers configured"
Make sure to register the server:
claude mcp add crashlytics -- node /path/to/dist/index.jsRestart Claude Code/Cursor IDE
2. "Authentication Failed"
Verify service account JSON file path is correct
Ensure service account has BigQuery permissions
Check project ID matches your Firebase project
3. "No crashes returned"
Confirm Crashlytics BigQuery export is enabled
Wait 24-48 hours for initial data export
Verify your app is actually sending crash data
4. "Table not found"
Check that
BIGQUERY_DATASET_IDis correct (usuallyfirebase_crashlytics)Ensure crashes exist in your Firebase project
Verify BigQuery export is working in Firebase Console
Debug Mode
Enable verbose logging:
DEBUG=mcp-crashlytics-server npm start🤝 Contributing
Fork the repository
Create a feature branch (
git checkout -b feature/amazing-feature)Make your changes
Add tests for new functionality
Commit your changes (
git commit -m 'Add amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
🔒 Security Considerations
⚠️ Never expose service account credentials in logs or version control
🔐 Use least-privilege permissions for service accounts
🔑 Store credentials securely using environment variables
🚫 Add
.envto.gitignore(already included)
📚 Resources
💡 Need Help?
🐛 Found a bug? Open an issue
💬 Have questions? Start a discussion
🚀 Want a feature? Request it here
Made with ❤️ for the MCP community
Available Tools
5 toolsanalyze_crash_trendsC
Analyze crash trends and statistics over time
Inputs: time_range (required), group_by.
get_anr_issuesB
Get ANR (Application Not Responding) issues for a specific app package name
Inputs: app_package (required), limit.
get_crash_detailsC
Get detailed information for a specific crash
Inputs: crash_id (required).
get_fatal_crashesB
Get fatal crashes for a specific app package name
Inputs: app_package (required), limit.
list_available_appsB
List all available apps in the Firebase Crashlytics dataset
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Hosted BigQuery MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Read-only Google Search Console MCP server for AI assistants.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.1162MIT
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol (MCP) server that brings your Google Tasks into Claude and other MCP-compatible clients, enabling task and task list management through natural conversation.19MIT
- AlicenseAqualityDmaintenanceAn MCP server for BigQuery that lets Claude answer questions about your search and analytics data, providing real analysis with verdicts and recommendations, not just raw query results.3244Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables LLMs to interact with Google BigQuery.MIT