Openfeature

dev.openfeaturePublished by openfeature.devv0.0.22Updated Oct 24, 2026

MCP server providing OpenFeature SDK installation guides and OFREP flag evaluation

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: dev.openfeature/mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to openfeature.dev. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/dev.openfeature%2Fmcp.svg)](https://sourceweft.com/mcp/dev.openfeature%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that gives an assistant OpenFeature SDK installation guides and OFREP feature flag evaluation.

What you can do: Provide OpenFeature SDK installation guidance for projects adopting the standard feature flag API. Evaluate feature flags through OFREP, the OpenFeature Remote Evaluation Protocol. The manifest lists no individual tools, so the exact operations are not documented in the supplied material.
When to use it: Useful when setting up OpenFeature in an application and wanting an assistant to walk through SDK installation, or when an assistant needs to evaluate flags through an OFREP endpoint.
Requirements: Runs as a local process on the user's machine, installed from the npm package @openfeature/mcp over stdio. Desktop only; no web execution. No authentication, environment variables or headers are declared, though an OFREP endpoint would presumably be needed for flag evaluation.

Before you install

The manifest declares no credentials, but flag evaluation connects to a flag management system, so flag data may leave the machine. No tools are listed, so review what it actually exposes before installing.

Installation

In SourceWeft

Open Openfeature in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.0.22LatestSep 16, 2026

Score

15% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
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.