Integration

Firebase Remote Config integration

Firebase Remote Config REST API for dynamic app configuration. Manage feature flags, A/B testing parameters, and app settings without deploying new versions. Supports version history, rollback, and platform-specific defaults.

Connect Firebase Remote Config How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Firebase Remote Config.Built from the 5 Firebase Remote Config tools below, on the connection you add once.

Common Firebase Remote Config use cases

version comparison
audit trail
config backup
config recovery
offline defaults
config deployment
A/B testing
app bundling
undo changes
config review

What you can do with Firebase Remote Config

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

download_defaultsDownload defaultsGETDownloads Remote Config default values in platform-specific format.
get_configGet configGETRetrieves the current or specific version of the Remote Config template.
list_versionsList versionsGETLists the version history of Remote Config templates.
rollback_configRollback configPOSTRolls back Remote Config to a previous version.
update_configUpdate configPUTUpdates the Remote Config template with new parameters and conditions.

Firebase Remote Config API rate limits

100 requests per second

Remote Config stores up to 300 versions for 90 days.

These are the limits Firebase Remote Config documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Firebase Remote Config documentation for current values.

Use Firebase Remote Config from Claude Code, Cursor or Codex

Connect Firebase Remote Config in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Firebase Remote Config operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Firebase Remote Config

Create your workspace
Sign up free. Nothing to install.
Connect Firebase Remote Config once
Add your Firebase Remote Config connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Firebase Remote Config integration FAQ

What can you do with the Firebase Remote Config integration?

LiveContext exposes 5 operations on Firebase Remote Config, covering remote config. Common uses include version comparison, audit trail and config backup.

What are the Firebase Remote Config API rate limits?

Firebase Remote Config documents 100 requests per second. Remote Config stores up to 300 versions for 90 days. Limits are set by Firebase Remote Config and can depend on your plan.