LaunchFlag

dev.launchflagPublished by launchflag.devOfficial publisherv0.2.7Updated Oct 24, 2026

Feature flags and kill switches. Turn a shipped feature off in production without a deploy.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

LaunchFlag gives an assistant access to a feature-flag service so shipped features can be toggled off in production without a deploy.

What you can do
  • Manage feature flags and kill switches through the LaunchFlag service.
  • Turn a shipped feature off in production without redeploying.
  • No tool list is published, so the exact operations available are not documented here.
When to use it
Useful when you want an assistant to help manage feature flags or kill switches, for example disabling a problematic feature in production without a deploy. Only add it if you already use LaunchFlag and are comfortable letting the assistant act on your flags.
Requirements
A LaunchFlag account and an API token from the dashboard Install page, supplied as LAUNCHFLAG_TOKEN or as an Authorization bearer header. Runs as a remote endpoint at launchflag.dev or as the local npm package launchflag-mcp over stdio; LAUNCHFLAG_URL can override the base URL.
Before you install
The token is a secret that grants access to your flags; keep it out of logs and shared configs. Flag changes can affect live production behavior, so review any action that disables or enables a feature before it is applied.

Installation

In SourceWeft

  1. Open LaunchFlag in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.launchflag%2Flaunchflag/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "launchflag": {
      "type": "http",
      "url": "https://launchflag.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.2.7LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.