
FireConfigMCP
An MCP server that provides access to Firebase Remote Config, allowing clients to interact with and manage Firebase remote configuration settings through the Model Context Protocol.
README
fire_config_mcp
Setup
1. Install dependencies
bun install
2. Create and place serviceAccount.json
To allow the server to access Firebase Remote Config, you need a Google Cloud service account key file:
A. Google Cloud Console (point‑and‑click)
- Open IAM & Admin → Service Accounts inside the same GCP project that owns your Firebase app.
- Click Create Service Account
- Name:
mcp-remote-config
(any name is fine) - Description: “MCP server – Remote Config access”
- Name:
- Grant this service account access:
- In the role picker, search for Remote Config Viewer or Remote Config Admin (as needed) and select it.
- Optionally add Firebase Analytics Viewer if your template conditions reference GA4 audiences.
- Finish → Done.
- In the list, click the account → Keys tab → Add Key → Create new key → JSON.
- Download the JSON file and place it in the project root as
serviceAccount.json
.
Note: Do not commit
serviceAccount.json
to version control. It is already in.gitignore
.
3. Run the server
bun run index.ts
The server will start on port 3000 by default.
Usage
Add this MCP server to a client (e.g., Cursor, Claude Desktop, or your own MCP client)
In Cursor:
- Open Cursor Settings → Features → Add new MCP server.
- For the command, use:
npx -y supergateway --sse http://localhost:3000/mcp
"fire-config-mcp": { "command": "npx", "args": [ "-y", "supergateway", "--sse", "http://localhost:3000/mcp" ] } ``` (Or use the path/command as configured in your environment.) 3. Save and connect.
In your own MCP client (TypeScript example):
You can connect to this server using the @modelcontextprotocol/sdk client:
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { SSEClientTransport } from "@modelcontextprotocol/sdk/client/sse.js";
const client = new Client({ name: "my-client", version: "1.0.0" });
const transport = new SSEClientTransport("http://localhost:3000/mcp");
await client.connect(transport);
// Now you can list tools, call tools, etc.
const tools = await client.listTools();
For more details, see the MCP TypeScript SDK documentation.
This project was created using bun init
in bun v1.2.7. Bun is a fast all-in-one JavaScript runtime.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.