Reflag

Created By
Reflag8 months ago
Create and manage feature flags. Enable your editor to understand your feature flags, their states, and their relationships within your codebase.
Overview

what is Reflag?

Reflag is a tool designed to create and manage feature flags, enabling developers to understand the states and relationships of feature flags within their codebase.

how to use Reflag?

To use Reflag, integrate it into your IDE with a one-click installation for supported editors like Cursor and VSCode. This allows your code editor to connect to the Reflag Model Context Protocol (MCP) server.

key features of Reflag?

  • Seamless integration with popular IDEs for feature flag management.
  • Standardized Model Context Protocol (MCP) for connecting AI models to data sources.
  • Real-time understanding of feature flags and their states within the codebase.

use cases of Reflag?

  1. Managing feature flags in a collaborative development environment.
  2. Enhancing AI-powered development tools with feature flag insights.
  3. Streamlining the feature management workflow in software projects.

FAQ from Reflag?

  • What are feature flags?

Feature flags are a software development technique that allows developers to enable or disable features without deploying new code.

  • How do I install Reflag?

You can install Reflag with one-click integration in supported IDEs like Cursor and VSCode.

  • Is Reflag free to use?

The pricing model for Reflag is not specified, please check the official documentation for details.

Server Config

{
  "mcpServers": {
    "Reflag": {
      "url": "https://app.reflag.com/api/mcp"
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
Reflag
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago