NetworkExperiments Claude Desktop Integration
This guide explains how to configure Claude Desktop (Mac and Windows) to use the NetworkExperiments API through the Model Context Protocol (MCP). The integration exposes 10 API endpointsas callable tools inside Claude's chat interface, including Gets a list of Network Experiment Profiles under a subscription, Gets a list of Network Experiment Profiles within a resource group under a subscription, Gets an NetworkExperiment Profile by ProfileName, and more. No API keys or credentials are needed — setup takes approximately 30 seconds. The server runs locally via npx and communicates over STDIO transport. Paste the JSON configuration below into your claude_desktop_config.json file to get started.
Integration Specs
Setup Instructions
Open Claude Settings
Launch Claude Desktop, open Settings (click your profile) → Developer → click 'Edit Config'.
Locate configuration file
This opens your local 'claude_desktop_config.json' file in your system editor.
Insert Server Config JSON
Paste the JSON configuration schema block (provided below) into the 'mcpServers' object.
Add authentication credentials
No credentials needed; leave the 'env' mapping empty.
Restart Claude app
Save the config file and restart Claude Desktop to load your new tools.
Configuration JSON
claude_desktop_config.jsonCopy and paste this config snippet inside your local configuration file.
{
"mcpServers": {
"azure-com-frontdoor-networkexperiment": {
"command": "npx",
"args": [
"-y",
"@mcp/azure-com-frontdoor-networkexperiment"
],
"env": {
"NETWORKEXPERIMENTS_API_KEY": "your_networkexperiments_api_key"
}
}
}
}Required Environment Keys
Provide these variable keys in your local environment section:
NETWORKEXPERIMENTS_API_KEYReplace your_networkexperiments_api_key with your secret key credentials.
Available Tools (10)
These endpoints are parsed from the OpenAPI schema and converted to Claude-compatible tools:
/subscriptions/{subscriptionId}/providers/Microsoft.Network/NetworkExperimentProfiles/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/Experiments/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/Experiments/{experimentName}/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/Experiments/{experimentName}/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/NetworkExperimentProfiles/{profileName}/Experiments/{experimentName}