Skip to content

Conversation

kenney
Copy link

@kenney kenney commented Apr 4, 2025

Goals

  • Get the MCP Firebase server working with local emulator
  • Add debugging (stdout and a /tmp file) to debug why MCP server would not instantiate
  • Add additional debugging for API calls

Can add more env options to control the logging, etc. as requested

@gannonh
Copy link
Owner

gannonh commented Apr 4, 2025

Hi @kenney - Thanks for the PR. These look like good ideas—the changes need tests to pass with 80% coverage. Let me know if this is something you can take on. If not, I may still merge the changes and add the test coverage when time permits. Thanks! 🙏

@gannonh
Copy link
Owner

gannonh commented Apr 4, 2025

Btw, in case you weren't aware, you can use the inspector tool to view logs while debugging. No need to write to a file (which will cause permission issues as an npm). I use a shell script to launch the inspector with env vars:

#!/bin/bash

# Export environment variables

export SERVICE_ACCOUNT_KEY_PATH="/absolute/path/to/yourp/firebaseServiceKey.json"
export FIREBASE_STORAGE_BUCKET="your-project-id.firebasestorage.app"

# Launch MCP Inspector with the server

npx @modelcontextprotocol/inspector "node" "/absolute/path/to//firebase-mcp/dist/index.js" 

@kenney
Copy link
Author

kenney commented Apr 10, 2025

Thanks, hadn't seen the inspector tool. I had been having issues getting any stdout/stderror feedback from Cursor with the firebase-mcp. I'll see if the inspector gives me what I need and remove the direct file debugging and work to get test coverage up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants