launchflag-mcp

MCPcommunitylive

v0.2.7Adarsh MishraMITUpdated todaynpm GitHub

MCP server that lets coding agents create and flip LaunchFlag flags.

Endpoint healthlive

checked 1h ago · 159ms · auth required

100% of the last 1 check reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1kDownloads/wk

todayLast update

Needs 1 credential before it runs

LAUNCHFLAG_TOKENAPI keyrequired
API token from the LaunchFlag dashboard Install page.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

AuthorAdarsh Mishra

LicenseMIT

Version0.2.7

Sourcenpm+mcp-registry

npmlaunchflag-mcp

GitHubadarshmishra07/flagship

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface8 tools · 1 privileged

Security scan✓ Cleanv0.2.7 · todayHow well does this scan work?

EvalsNone

IndexedSep 9, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · 1 privileged

Statically extracted from the published packagev0.2.7 · 1h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

list_flagsList every LaunchFlag flag with its dev, staging and prod state.

List every LaunchFlag flag with its dev, staging and prod state.

No input schema was published for this tool.

cleanup_flagsFlags whose code can now be removed, with the reason and what to do about each. Run this when asked to tidy up feature flags, or after finishing a rollout. Two kinds: settled flags are on for everyone everywhere and still evaluated constantly, so the branch around them has one reachable side; stale…

Flags whose code can now be removed, with the reason and what to do about each. Run this when asked to tidy up feature flags, or after finishing a rollout. Two kinds: settled flags are on for everyone everywhere and still evaluated constantly, so the branch around them has one reachable side; stale…

No input schema was published for this tool.

create_flagCreate a flag, OFF in every environment, so a risky change can ship dark. Returns the code snippet to wrap the new path in.

Create a flag, OFF in every environment, so a risky change can ship dark. Returns the code snippet to wrap the new path in.

No input schema was published for this tool.

set_flagTurn a flag on or off, or change who it targets, in one environment. Environments are always dev, staging and prod here, whatever the project calls them on its dashboard.

Turn a flag on or off, or change who it targets, in one environment. Environments are always dev, staging and prod here, whatever the project calls them on its dashboard.

No input schema was published for this tool.

promote_flagCopy one environment's flag config forward: dev to staging, staging to prod, or dev straight to prod on a project that does not run staging. A project may label those environments differently, and plans with two environments have no staging slot at all.

Copy one environment's flag config forward: dev to staging, staging to prod, or dev straight to prod on a project that does not run staging. A project may label those environments differently, and plans with two environments have no staging slot at all.

No input schema was published for this tool.

delete_flagprivilegedDelete a flag. Only once the code paths behind it are gone.

Delete a flag. Only once the code paths behind it are gone.

No input schema was published for this tool.

emergency_offKill switch: disable every non-essential flag in the project at once, or lift it.

Kill switch: disable every non-essential flag in the project at once, or lift it.

No input schema was published for this tool.

list_projectsList your LaunchFlag projects and their env keys.

List your LaunchFlag projects and their env keys.

No input schema was published for this tool.

8 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server that lets coding agents create and flip LaunchFlag flags.

Keywords

mcpmodel context protocolfeature flagsfeature-flagskill switchrolloutlaunchdarkly alternativenext.js

Alternatives

Comparing tool surfaces…

Tools exposed

8 tools · 1 privileged · observed 2026-09-09 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

list_flags
cleanup_flags
create_flag
set_flag
promote_flag
delete_flagpriv
emergency_off
list_projects

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-09 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.5.4
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.7
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.5.4shown above
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.7
- jose6.2.12
- express5.2.1+26 not drawn2 dependencies
  - vary1.1.2shown above
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 48
below the depth cap: 5

http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached
path-to-regexp ^8.0.0 — required by router@2.2.0package cap reached

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.