FeatureClient MCP Config
Azure Feature Exposure Control (AFEC) provides a mechanism for the resource providers to control feature exposure to users. Resource providers typically use this mechanism to provide public/private preview for new features prior to making them generally available. Users need to explicitly register f
Config URL
Use this URL in any MCP-compatible client to fetch the config automatically.
https://mcp-bridge.pages.dev/config/azure-com-resources-features.jsonConfiguration JSON
Use curl https://mcp-bridge.pages.dev/config/azure-com-resources-features.json to fetch programmatically.
{
"mcpServers": {
"azure-com-resources-features": {
"command": "npx",
"args": ["-y","@mcp/azure-com-resources-features"],
"env": {
"FEATURECLIENT_API_KEY": "your_featureclient_api_key"
}
}
}
}How to Use
Cursor
Go to Cursor Settings → MCP Servers → Add with the JSON above.
CLI / curl
Fetch the config programmatically:
curl https://mcp-bridge.pages.dev/config/azure-com-resources-features.jsonEnvironment Variables
FEATURECLIENT_API_KEYReplace your_featureclient_api_key with your actual featureclient api key
Endpoints
GET
/providers/Microsoft.Features/operationsListOperations
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Features/featuresFeatures_ListAll
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/featuresFeatures_List
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features/{featureName}Features_Get
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Features/providers/{resourceProviderNamespace}/features/{featureName}/registerFeatures_Register