Flagbearer

dev.flagbearer/flagbearerVersion 1.0.1

Feature flags for coding agents: create flags, roll them out gradually and write the flag code.

Status

Responds507 msNov 14, 2026, 14:26 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:26 UTC
Latency: 507 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://mcp.flagbearer.dev/Responds507 msNov 14, 2026, 14:26 UTC

No sign-in

Claude Code

claude mcp add --transport http flagbearer https://mcp.flagbearer.dev/

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: flagbearer
Remote MCP server URL: https://mcp.flagbearer.dev/

Cursor

{
  "mcpServers": {
    "flagbearer": {
      "url": "https://mcp.flagbearer.dev/"
    }
  }
}

VS Code

code --add-mcp '{"name":"flagbearer","type":"http","url":"https://mcp.flagbearer.dev/"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

9 tools

Tools of Flagbearer
	Description		Read-only	Idempotent	Open world
`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. Call this when flags aren't behaving as expected, and after adding flag code and running the app.	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. Call this when flags aren't behaving as expected, and after adding flag code and running the app.	Not declared	Yes	Not declared	Not declared
`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.	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.	Not declared	Not declared	Not declared	Not declared
`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 @flagbearer/web (React and browser apps), @flagbearer/node or @flagbearer/react-native. Call it when setting up flags in such a project, and again after creating a flag.	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 @flagbearer/web (React and browser apps), @flagbearer/node or @flagbearer/react-native. Call it when setting up flags in such a project, and again after creating a flag.	Not declared	Yes	Not declared	Not declared
`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 that checks a flag, and follow it.	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 that checks a flag, and follow it.	Not declared	Yes	Not declared	Not declared
`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 result. Use it when a bug report says a feature stopped working, or works for some users and not others. times is a list of ISO timestamps to show side by side, like before and after a report; leave it out for now. An email the SDK saw with several user keys gives one entry per key.	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 result. Use it when a bug report says a feature stopped working, or works for some users and not others. times is a list of ISO timestamps to show side by side, like before and after a report; leave it out for now. An email the SDK saw with several user keys gives one entry per key.	Not declared	Yes	Not declared	Not declared
`list_applications`List the applications in an organization. Flags belong to an application.	List the applications in an organization. Flags belong to an application.	Not declared	Yes	Not declared	Not declared
`list_flags`List an application's feature flags with whether each is on, and its rollout percent, in every environment.	List an application's feature flags with whether each is on, and its rollout percent, in every environment.	Not declared	Yes	Not declared	Not declared
`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, and ask them to reconnect and approve the right organization.	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, and ask them to reconnect and approve the right organization.	Not declared	Yes	Not declared	Not declared
`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 rolloutPercent it's 0, which turns it on only for the environment's testers. Changing production needs confirmProduction: true. Only send that after the user has confirmed the change.	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 rolloutPercent it's 0, which turns it on only for the environment's testers. Changing production needs confirmProduction: true. Only send that after the user has confirmed the change.	Not declared	Not declared	Yes	Not declared

Details

Registry status: Active
Published: Nov 12, 2026
Updated: Nov 12, 2026
Website: https://docs.flagbearer.dev/sdks/mcp⁠ (opens in a new tab)
Repository: https://github.com/flagbearer-dev/sdks⁠ (opens in a new tab)
Categories (suggested): Developer toolsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing