Scaffold Flags Integration
scaffold_flags_integrationScaffold a flags-only Bridge integration into an existing project — the MCP equivalent of bridge flag init. Returns everything that command produces, for YOU to write to disk: the contents of bridge-flags.config.json (app id, app name, base URL, suggested provider config, read live from this Bridge app), the install command, and the framework-specific setup guide fetched from the plugin repo that owns it. Writes nothing — neither to disk nor to the Bridge app. Call this when adding feature flags to a project for the first time; for auth or billing use get_integration_guide with topic=master or topic=billing-master instead. framework is REQUIRED: this server cannot see the caller's disk, so detect it yourself from package.json (next → nextjs, @sveltejs/kit or svelte → svelte, @nestjs/core → nestjs, @angular/core → angular, react → react, express → express; check in that order) and pass it. The returned guide is the same document get_integration_guide returns for topic=feature-flags, so there is no need to call both. Do not invent import specifiers — they differ per plugin and only the guide has the current ones.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| app | No | Id of the Bridge app to act on for this call (see list_apps). Omit to use the current app. | |
| baseUrl | No | Bridge API base URL to write into the config. Defaults to the one of the Bridge environment this server runs in. Pass it only when the project should talk to a different Bridge environment. | |
| framework | Yes | The framework the target project uses. Required — the server cannot see the caller's disk. Detect it from the project's package.json dependencies. | |
| includeGuide | No | Whether to fetch and inline the framework setup guide. Defaults to true. Pass false only when you have already read it via get_integration_guide and want just the config. |