Fireconfigmcp

You run a local MCP server that exposes Firebase Remote Config access and a set of tools you can use from clients. This server lets your MCP clients discover available tools, execute them, and receive results over HTTP or via a local stdio process started by your runtime. It is designed to be easy to run in development, staging, and production environments while keeping credentials private and separate per environment.

How to use

To use this MCP server, start it for the environments you need and connect your MCP clients to the provided HTTP endpoint or to the local process if you prefer a stdio setup.

Starting the server for multiple environments is done with a single command. The server will expose its MCP API on port 3000 by default, and the HTTP endpoint will be at /mcp.

Connecting from an MCP client is straightforward. You can use the HTTP URL to communicate with the server, or run the server locally as a stdio process and connect through the provided command. Here are two common usage patterns.

In Cursor, add a new MCP server and configure the command to point to the HTTP endpoint.

If you are using your own MCP client, you can connect to the server via the following TypeScript example to access the list of tools and execute actions.

How to install

Prerequisites: ensure you have Bun installed and available in your shell.

Install dependencies for the MCP server.

bun install

Additional sections

Security and environment setup are important when dealing with credentials for Firebase Remote Config. You will work with a Google Cloud service account JSON file per environment to grant the MCP server access to Remote Config.

Create and configure a Google Cloud service account for Remote Config access. This includes granting Remote Config Admin or Viewer roles and downloading a JSON key file. Keep this file secure and do not commit it to version control.

Place each environment's service account file in your project root with a clear name.

• development: serviceAccount_dev.json
• staging: serviceAccount_stg.json
• production: serviceAccount_prod.json

When you run the server, specify the environments you want to load. If you pass dev, stg, and prod, all three environments will be loaded. If you omit arguments, dev is loaded by default.

The server defaults to listening on port 3000.

Usage example to start multiple environments in one command.

bun run index.ts dev stg prod

Available tools

listTools

Fetches the list of available MCP tools exposed by the server.

callTool

Executes a specified tool against the server to perform actions or retrieve data.