npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@frontmcp/plugin-feature-flags

v1.6.1

Published

Feature flag plugin for FrontMCP - dynamically gate MCP capabilities behind feature flags

Readme

@frontmcp/plugin-feature-flags

Gate MCP capabilities behind feature flags — hide tools, branch behaviour, and roll out changes per user without redeploying.

NPM

Install

npm install @frontmcp/plugin-feature-flags

Usage

import { FeatureFlagPlugin } from '@frontmcp/plugin-feature-flags';
import { FrontMcp } from '@frontmcp/sdk';

@FrontMcp({
  info: { name: 'my-server', version: '1.0.0' },
  apps: [MyApp],
  plugins: [
    FeatureFlagPlugin.configure({
      provider: 'static',
      flags: { 'new-search': true, 'beta-export': false },
    }),
  ],
})
class Server {}

Then read flags from any tool through this.featureFlags:

@Tool({ name: 'search', inputSchema: { q: z.string() } })
export default class SearchTool extends ToolContext {
  async execute({ q }: { q: string }) {
    if (await this.featureFlags.isEnabled('new-search')) {
      return newSearch(q);
    }
    return legacySearch(q);
  }
}

Providers

| Provider | provider | Notes | | ------------ | ---------------- | ------------------------------------------------ | | Static | 'static' | Flags from config. Good for local dev and tests. | | Split.io | 'splitio' | Requires an SDK key. | | LaunchDarkly | 'launchdarkly' | Requires an SDK key. | | Unleash | 'unleash' | Requires a URL + API token. | | Custom | 'custom' | Supply your own FeatureFlagAdapter. |

FeatureFlagPlugin.configure({
  provider: 'launchdarkly',
  sdkKey: process.env.LD_SDK_KEY,
  // Which identity the flag is evaluated for. Defaults to the session's user.
  userIdResolver: (ctx) => ctx.authInfo?.clientId,
  attributesResolver: (ctx) => ({ plan: ctx.authInfo?.extra?.plan }),
});

Custom adapter

import { FeatureFlagPlugin, type FeatureFlagAdapter } from '@frontmcp/plugin-feature-flags';

const adapter: FeatureFlagAdapter = {
  async isEnabled(key, ctx) {
    return myBackend.check(key, ctx.userId);
  },
};

FeatureFlagPlugin.configure({ provider: 'custom', adapter });

API

this.featureFlags (an injected FeatureFlagAccessor):

| Method | Returns | Purpose | | -------------------------- | ------------------------------- | --------------------------------------------- | | isEnabled(key, default?) | Promise<boolean> | Evaluate one boolean flag | | getVariant(key) | Promise<FeatureFlagVariant> | Multivariate flag value | | evaluateFlags(keys) | Promise<Map<string, boolean>> | Batch evaluation in one round trip | | resolveRef(ref) | Promise<boolean> | Resolve a flag reference ({ flag, negate }) |

Outside a tool, use getFeatureFlags() / tryGetFeatureFlags().

Failure behaviour

If the provider is unreachable, isEnabled returns the defaultValue you pass (or false). Always pass an explicit default for a flag that gates something important, so an outage degrades the way you intend rather than silently disabling a feature.

Full guide: Feature Flags

License

Apache-2.0