Skip to main content
Glama
OpenFeature MCP Server

OpenFeature MCP Server

Archived: MIGRATED TO OPENFEATURE ORG

OpenFeature MCP Local Server (stdio)

Warning

This project is in active development.

Related MCP server: Langfuse Prompt Management MCP Server

Features

A local Model Context Protocol (MCP) server that provides OpenFeature SDK installation guidance and Open Feature Remote Evaluation Protocol (OFREP) over stdio.

  • OpenFeature SDK Installation Guides: Fetch installation prompts for various OpenFeature SDKs

  • MCP stdio Transport: Intended for local usage by MCP-compatible clients

Configure your AI client (local)

Cursor

Add to ~/.cursor/mcp_settings.json:

{
  "mcpServers": {
    "OpenFeature": {
      "command": "npx",
      "args": ["-y", "@openfeature/mcp"]
    }
  }
}

VS Code (Continue)

Add to .continue/config.json:

{
  "mcpServers": {
    "OpenFeature": {
      "command": "npx",
      "args": ["-y", "@openfeature/mcp"]
    }
  }
}

Claude Code (CLI)

Add the server via CLI:

claude mcp add --transport stdio openfeature npx -y @openfeature/mcp

Then manage the connection in the CLI with /mcp.

Windsurf

In the "Manage MCP servers" raw config, add:

{
  "mcpServers": {
    "OpenFeature": {
      "command": "npx",
      "args": ["-y", "@openfeature/mcp"]
    }
  }
}

Claude Desktop

Edit your Claude Desktop config and add:

{
  "mcpServers": {
    "openfeature": {
      "command": "npx",
      "args": ["-y", "@openfeature/mcp"]
    }
  }
}

Restart Claude Desktop after saving.

NPM Global install (optional)

If you prefer a global install instead of NPX:

npm install -g @openfeature/mcp

Now in your MCP config use openfeature-mcp as the command:

{
  "mcpServers": {
    "openfeature": {
      "command": "openfeature-mcp"
    }
  }
}

All logs are written to stderr. The MCP protocol messages use stdout.

Available Tools

install_openfeature_sdk

Fetches Markdown instructions for installing the OpenFeature SDK for a given technology. Optionally augments the prompt with installation guidance for one or more feature flag providers.

Parameters:

  • technology (string enum): One of the supported technologies listed below

  • providers (string array, optional): Zero or more provider identifiers. If present, adds provider-specific installation notes to the prompt (or removes placeholder sections when empty).

Supported Technologies:

The technologies list is build from the avaliable prompts/*.md, updated automatically using scripts/build-prompts.js

  • android

  • dotnet

  • go

  • ios

  • java

  • javascript

  • nestjs

  • nodejs

  • php

  • python

  • react

  • ruby

Supported Providers:

The provider list is sourced automatically from the OpenFeature open-feature/openfeature.dev repo; newly added providers there become available here without manual edits. See scripts/build-providers.js for details.

ofrep_flag_eval

Evaluate feature flags via OpenFeature Remote Evaluation Protocol (OFREP). If flag_key is omitted, performs bulk evaluation.

References: open-feature/protocol repo, OFREP OpenAPI spec

Parameters (all optional unless noted):

  • base_url (string, optional): Base URL of your OFREP-compatible flag service. If omitted, the server uses env/config (see below).

  • flag_key (string, optional): If provided, calls single flag evaluation: /ofrep/v1/evaluate/flags/{key}. If omitted, calls bulk: /ofrep/v1/evaluate/flags.

  • context (object, optional): Evaluation context, e.g. { "targetingKey": "user-123", ... }.

  • etag (string, optional): For bulk requests, sent as If-None-Match to enable 304 caching semantics.

  • auth (object, optional): Inline auth for this call only.

    • bearer_token (string, optional): Sets Authorization: Bearer <token>.

    • api_key (string, optional): Sets X-API-Key: <key>.

Auth and base URL resolution (priority):

  1. Tool call args: base_url, auth.bearer_token, auth.api_key

  2. Environment variables: OPENFEATURE_OFREP_BASE_URL (or OFREP_BASE_URL), OPENFEATURE_OFREP_BEARER_TOKEN (or OFREP_BEARER_TOKEN), OPENFEATURE_OFREP_API_KEY (or OFREP_API_KEY)

  3. Config file: ~/.openfeature-mcp.json (override with OPENFEATURE_MCP_CONFIG_PATH)

Example ~/.openfeature-mcp.json:

{
  "OFREP": {
    "baseUrl": "https://flags.example.com",
    "bearerToken": "<token>",
    "apiKey": "<key>"
  }
}

Notes:

  • Bulk requests may return ETag. Pass it back via etag to leverage 304 Not Modified.

  • Either bearer token or API key can be supplied; both are supported by the spec.

Development

Prerequisites

  • Node.js 18+

Setup

  1. Install dependencies:

    npm install
  2. Add or edit install guides in the prompts/ folder (Markdown). These are bundled at build time.

  3. Build prompts bundle:

    npm run build-prompts
  4. Build TypeScript:

    npm run build
  5. Run locally (binary entrypoint):

    node dist/cli.js

Available Tools

1 tool
install_openfeature_sdkB

Fetch and return OpenFeature install prompt Markdown by guide name. Available guides: android, dotnet, go, ios, java, javascript, nestjs, nodejs, php, python, react, ruby. Input: { guide: string }

Inputs: guide (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clear purpose: fetching OpenFeature SDK installation prompts by guide name.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect. The tool name 'install_openfeature_sdk' follows a clear verb_noun pattern and is descriptive of its function.

    Tool Count2/5

    A single tool is too few for a server named 'OpenFeature MCP Server', which suggests a broader scope related to feature flag management. This minimal set severely limits functionality and agent workflows, making it feel incomplete and under-scoped.

    Completeness1/5

    The tool set is severely incomplete for the apparent domain of OpenFeature (feature flag management). It lacks core operations like creating, updating, or evaluating feature flags, managing providers, or accessing flag configurations, leaving significant gaps that will cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides OpenFeature SDK installation guidance for various programming languages and enables feature flag evaluation through the OpenFeature Remote Evaluation Protocol (OFREP). Supports multiple AI clients and can connect to any OFREP-compatible feature flag service.
      194 npm
      3
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to list and retrieve Langfuse prompts, including text and chat prompts, compiling them with user-supplied variables. It also exposes equivalent tools so clients without prompt capability can still discover and fetch prompts.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Desktop and Cursor to discover, list, and retrieve prompts stored in Langfuse, compiling them with supplied variables on demand. It exposes both prompt capabilities and equivalent tools so clients without prompt support can still fetch prompts (limited to those labeled production).
      -