$HEADLESS SYSTEMS
03 / Scorecard / Feature Flags & Config

Firebase Remote Config

B
Headless Index
74/100
JAIRF
N/A
Verified
AUG 20, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Firebase Remote Config earns Band B in the Feature Flags & Config category of The Headless Index, with a thesis-fit score of 74/100. Its strongest dimension is schema observability (17/20); its weakest scored dimension is webhooks and events (12/20). No public OpenAPI specification was found when Firebase Remote Config was scored, which limits how far an agent can go without human integration work.

Editorial verdict
Firebase Remote Config is solidly built for programmatic consumption. The Headless Index thesis-fit score of 74/100 lands it in the upper-middle of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Firebase Remote Config lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Remote Config is reachable programmatically, but the shape betrays its origin. The whole configuration is one document: GET and PUT on firebaseremoteconfig.googleapis.com/v1/projects/{project}/remoteConfig, guarded by an ETag, with no per-parameter CRUD. Server work goes through the Admin SDK (firebase-admin getTemplate and publishTemplate); client SDKs only fetch and activate. An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Template work is fully scriptable through the CLI (firebase remoteconfig:get, remoteconfig:versions:list, remoteconfig:rollback), and the JSON is checkable into git. Everything around the template is not. Rollouts, personalization and A/B experiments are console features with no equivalent endpoints, and no Terraform resource models a Remote Config template. Agents can publish parameters; they cannot run a staged rollout unattended.[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Firebase built its MCP server into the CLI itself, and Remote Config got a slot: src/mcp/tools/remoteconfig (github.com/firebase/firebase-tools) ships get_template.ts and update_template.ts, and the registry lists io.github.firebase/firebase-mcp. Two tools is the whole surface, mirroring the template-level API, so an agent can read and rewrite the document but cannot reason about individual conditions or rollouts.[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. One event exists. Publishing a template emits google.firebase.remoteconfig.remoteConfig.v1.updated, consumed as a Cloud Functions trigger (functions.remoteConfig.onConfigUpdated) carrying version number, update type, origin and the updating user. Delivery, retry and ordering are Eventarc's, not Firebase's, and there is no HTTP webhook, no signing scheme and no replay. Config change is visible; nothing finer than the whole template is. Net assessment: Firebase Remote Config can be operated by agents for the majority of practical workflows. The closest thing to a gap is webhooks and events[3], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent15/20
scored

Remote Config is reachable programmatically, but the shape betrays its origin. The whole configuration is one document: GET and PUT on firebaseremoteconfig.googleapis.com/v1/projects/{project}/remoteConfig, guarded by an ETag, with no per-parameter CRUD. Server work goes through the Admin SDK (firebase-admin getTemplate and publishTemplate); client SDKs only fetch and activate. Concurrent agents editing one template will fight over that ETag.

signals (6)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • −OpenAPI specNot found across 17 probe paths
  • −GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
  • +SDKs maintained13 (dotnet, go, java, javascript, python, ruby, swift, typescript); top by stars: firebase/firebase-js-sdk (5136 stars)
  • +SDK recency11 of 13 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-19)
  • +npm weekly downloads9.4M across published packages; top: firebase-admin @ 7.4M/week
cite (1)
  • github.sdks@2026-08-19
Headless operation14/20
scored

Template work is fully scriptable through the CLI (firebase remoteconfig:get, remoteconfig:versions:list, remoteconfig:rollback), and the JSON is checkable into git. Everything around the template is not. Rollouts, personalization and A/B experiments are console features with no equivalent endpoints, and no Terraform resource models a Remote Config template. Agents can publish parameters; they cannot run a staged rollout unattended.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • −API operations exposedNo OpenAPI spec; operations count unknown
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (1)
  • ai_review_browser.topics_found@2026-08-19
MCP & agent posture16/20
scored

Firebase built its MCP server into the CLI itself, and Remote Config got a slot: src/mcp/tools/remoteconfig (github.com/firebase/firebase-tools) ships get_template.ts and update_template.ts, and the registry lists io.github.firebase/firebase-mcp. Two tools is the whole surface, mirroring the template-level API, so an agent can read and rewrite the document but cannot reason about individual conditions or rollouts.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • −Official MCP serverNone found in vendor's GitHub org or the official MCP registry
  • −Community MCP serversNone found
  • +Agent-friendly SDKs3 TS/JS SDKs available; top: firebase-functions (2.1M/week downloads)
cite (1)
  • ai_review_browser.mcp@2026-08-19
Schema observability17/20
scored

A machine-readable contract is one fetch away. The Google Discovery document (firebaseremoteconfig.googleapis.com/$discovery/rest?version=v1) returns roughly 135KB of JSON, revision 20260819, enumerating every method and schema. It is Discovery rather than OpenAPI, so generic generators need a conversion step, but an agent can build a working client without reading a single prose page.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • −OpenAPINot discovered across 17 standard probe paths
  • −GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)
cite (1)
  • ai_review_browser.pages_fetched@2026-08-19
Webhooks & events12/20
scored

One event exists. Publishing a template emits google.firebase.remoteconfig.remoteConfig.v1.updated, consumed as a Cloud Functions trigger (functions.remoteConfig.onConfigUpdated) carrying version number, update type, origin and the updating user. Delivery, retry and ordering are Eventarc's, not Firebase's, and there is no HTTP webhook, no signing scheme and no replay. Config change is visible; nothing finer than the whole template is.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • ai_review_browser.pages_fetched@2026-08-19
JAIRF · 6 dimensions
JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Powered by JAIRF v1.0.0 by Jentic

Band rationale:B band: JAIRF=N/A HeadlessIndex=74

04 / Embed

Show Firebase Remote Config's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Firebase Remote Config mini badge preview
Get embed code
Peers in Feature Flags & Config
GrowthBookB
Headless Index 74/100
FeatBitB
Headless Index 79/100
FlagsmithB
Headless Index 68/100
See full Feature Flags & Config ranking →
FAQ

Firebase Remote Config and agent readiness

Is Firebase Remote Config agent-ready?
Firebase Remote Config scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is schema observability; its weakest is webhooks and events.
Does Firebase Remote Config publish an OpenAPI spec?
No published OpenAPI specification was found when Firebase Remote Config was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Firebase Remote Config's Headless Index score?
Firebase Remote Config scores 74/100 on the Headless Index thesis-fit rubric and sits in Band B in the Feature Flags & Config category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.