OpenFeature MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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 } |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.