← Nesim Apps

Reading Crashlytics From an AI Coding Assistant: The Project Folder Trap

By Nesim Razon, independent mobile developer · 2026-11-20

#Dev notes#Android

If your AI coding assistant is connected to the Firebase MCP server but cannot see any Crashlytics tools, the cause is probably the project folder, not a broken login. The server turns tools on according to the Firebase SDKs it finds in the folder it is pointed at. Point it at an Android app that uses Crashlytics and the tools appear. Here is how I found that out and the checks I run before I trust a report.

The symptom

I asked the assistant to check crash reports for a few apps. It could list apps and read project details, but there were no Crashlytics tools at all. Reconnecting the server and signing in again changed nothing, and the login was fine, since other Firebase tools worked.

The cause: tools follow the project folder

The Firebase MCP server enables some tools automatically, based on the Firebase SDKs it detects in the project directory it uses. My default directory held a small Firebase config for a dashboard project that has no Crashlytics SDK, so the server never offered the Crashlytics tools.

The fix without editing config files

The environment can be changed from inside the session. I called the environment update tool with the project directory set to an Android app folder that does use Crashlytics, together with the Firebase project for that app. After that, searching for “crashlytics” in the tool list returned the report and issue tools. No settings file was touched.

Read the guide before the first report

The server also publishes a guide as a resource, with the right way to request reports. Reading it first saved me from guessing at filters. It is a short read and it explains which report types exist and what each one needs.

Check the active project every time

Tools act on the active Firebase project. Once I created an app in the wrong project because the active one was different from what I assumed. Now, before any write action, I ask the server for the current environment and compare the project identifier with the one I mean.

Do not read an error as “no crashes”

One app returned a 404 when I asked for its top issues. That did not mean zero crashes. For that app crash data collection is switched off on purpose, so there is nothing to read. A report is only meaningful if collection is on for the app and the build you care about, so I note which apps are covered before I call a release clean.

Checklist

Frequently asked questions

Why does the Firebase MCP server show no Crashlytics tools?

The server enables tools based on the Firebase SDKs found in its project directory. If that folder has no Crashlytics SDK, the Crashlytics tools stay hidden.

How do I make the Crashlytics tools appear?

Update the server environment so the project directory is an app folder that uses Crashlytics and set the matching Firebase project. Then search the tool list again.

Does a 404 on top issues mean the app has no crashes?

No. It can mean crash collection is off for that app, so there is no data to return.

Do I have to edit a config file?

Not necessarily. The environment update tool can change the directory and the active project during the session.

More from the blog