Skip to content
Cloud InfrastructureClaude Desktop Guide

NetworkManagementClient Claude Desktop Integration

This guide explains how to configure Claude Desktop (Mac and Windows) to use the NetworkManagementClient API through the Model Context Protocol (MCP). The integration exposes 10 API endpointsas callable tools inside Claude's chat interface, including PrivateLinkServices_ListAutoApprovedPrivateLinkServices, PrivateLinkServices_CheckPrivateLinkServiceVisibility, PrivateLinkServices_ListBySubscription, 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

ClientClaude Desktop
Runtimenpx
AuthenticationNone
Setup Time~30 sec

Setup Instructions

1

Open Claude Settings

Launch Claude Desktop, open Settings (click your profile) → Developer → click 'Edit Config'.

2

Locate configuration file

This opens your local 'claude_desktop_config.json' file in your system editor.

3

Insert Server Config JSON

Paste the JSON configuration schema block (provided below) into the 'mcpServers' object.

4

Add authentication credentials

No credentials needed; leave the 'env' mapping empty.

5

Restart Claude app

Save the config file and restart Claude Desktop to load your new tools.

Configuration JSON

claude_desktop_config.json

Copy and paste this config snippet inside your local configuration file.

{
  "mcpServers": {
    "azure-com-network-privatelinkservice": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp/azure-com-network-privatelinkservice"
      ],
      "env": {
        "NETWORKMANAGEMENTCLIENT_API_KEY": "your_networkmanagementclient_api_key"
      }
    }
  }
}

Required Environment Keys

Provide these variable keys in your local environment section:

NETWORKMANAGEMENTCLIENT_API_KEY

Replace your_networkmanagementclient_api_key with your secret key credentials.

Available Tools (10)

These endpoints are parsed from the OpenAPI schema and converted to Claude-compatible tools:

GET/subscriptions/{subscriptionId}/providers/Microsoft.Network/locations/{location}/autoApprovedPrivateLinkServices
PrivateLinkServices_ListAutoApprovedPrivateLinkServices
POST/subscriptions/{subscriptionId}/providers/Microsoft.Network/locations/{location}/checkPrivateLinkServiceVisibility
PrivateLinkServices_CheckPrivateLinkServiceVisibility
GET/subscriptions/{subscriptionId}/providers/Microsoft.Network/privateLinkServices
PrivateLinkServices_ListBySubscription
GET/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/locations/{location}/autoApprovedPrivateLinkServices
PrivateLinkServices_ListAutoApprovedPrivateLinkServicesByResourceGroup
POST/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/locations/{location}/checkPrivateLinkServiceVisibility
PrivateLinkServices_CheckPrivateLinkServiceVisibilityByResourceGroup
GET/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/privateLinkServices
PrivateLinkServices_List
GET/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/privateLinkServices/{serviceName}
PrivateLinkServices_Get
PUT/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/privateLinkServices/{serviceName}
PrivateLinkServices_CreateOrUpdate
DELETE/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/privateLinkServices/{serviceName}
PrivateLinkServices_Delete
PUT/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/privateLinkServices/{serviceName}/privateEndpointConnections/{peConnectionName}
PrivateLinkServices_UpdatePrivateEndpointConnection