Flagbearer
dev.flagbearer/flagbearer · v1.0.1 · MCP 2025-06-18
Feature flags for coding agents: create flags, roll them out gradually and write the flag code.
Reachability
reachable
checked 2026-11-21 05:38 UTC
Registry status active
Tools pinned 11
90bb5d2c2948
Tools last changed
2026-11-17
Repo last push 2026-11-12
as of 2026-11-21
GitHub stars 0
as of 2026-11-21
Provenance
Registry namespace dev.flagbearer
(domain verified by the official registry)
Repository
github.com/flagbearer-dev/sdks
Remote endpoints
https://mcp.flagbearer.dev (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-11-17 05:34 | tools changed | 2 added, 0 removed, 0 changed |
| 2026-11-13 05:30 | first capture | 9 tools pinned |
Pinned tool definitions (11)
| Tool | Description |
|---|---|
| list_organizations | List the Flagbearer organizations you belong to. Start here to find an organization's ID. This connection only covers the organizations listed. If the project's application isn't in any of them, tell the user before writing flag code,... |
| list_applications | List the applications in an organization. Flags belong to an application. |
| create_application | Create an application in an organization, usually one per product or codebase, like Storefront. It comes with development, staging and production environments. Ask the user for the name if it isn't obvious from the project. Then create... |
| list_flags | List an application's feature flags with whether each is on, and its rollout percent, in every environment. |
| create_flag | Create a feature flag in an application. It starts off in every environment; use set_flag to turn it on. The key is what code checks, like new-checkout. |
| set_flag | Turn a flag on or off in one environment, by flag key and environment key. When turning a flag on, rolloutPercent says who gets it: 100 for everyone, or a percentage of users. Ask the user whether it should be on for everyone. Without... |
| generate_flag_types | The text of a TypeScript file listing an application's flag keys, so a misspelled key is a type error and editors autocomplete keys. Write the returned text to the path exactly as it is, and commit it. Only for TypeScript projects using... |
| get_user_flags | What a user should have got for every flag in one environment, by email or user key, with the reason (off, tester or rollout and their bucket), what their SDK reported that UTC day (seen), and any changes that day that flipped their... |
| get_sdk_docs | The current Flagbearer SDK docs for a platform (react, react-native, ios, android, browser, node, python, go, java, dotnet, ruby, rust, cpp or php), plus one environment's SDK address and public client key. Call this before writing code... |
| create_client_key | Create a public client key for one environment, for browser and mobile SDKs (react, react-native, ios, android, browser). It's safe in app code. Each environment needs its own. Server SDKs need a secret server key instead, which only an... |
| check_sdk_setup | What looks wrong with how an application's SDKs are set up, per environment, from what they sent in the last day: flags the code checks that don't exist, wrong or leaked keys, old SDK versions, and environments nothing has connected to.... |
Get alerted when this changes.
Email the moment dev.flagbearer/flagbearer drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/dev.flagbearer/flagbearer)
Maintain this server? Add the badge to your README. It links your users to this live status page.