Skip to content
MCP-Bridge
Cloud InfrastructureClaude Desktop Guide

AzureDigitalTwinsManagementClient Claude Desktop Integration

This guide explains how to configure Claude Desktop (Mac and Windows) to use the AzureDigitalTwinsManagementClient API through the Model Context Protocol (MCP). The integration exposes 10 API endpointsas callable tools inside Claude's chat interface, including Operations_List, DigitalTwins_List, DigitalTwins_CheckNameAvailability, 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-digitaltwins": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp/azure-com-digitaltwins"
      ],
      "env": {
        "AZUREDIGITALTWINSMANAGEMENTCLIENT_API_KEY": "your_azuredigitaltwinsmanagementclient_api_key"
      }
    }
  }
}

Required Environment Keys

Provide these variable keys in your local environment section:

AZUREDIGITALTWINSMANAGEMENTCLIENT_API_KEY

Replace your_azuredigitaltwinsmanagementclient_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/providers/Microsoft.DigitalTwins/operations
Operations_List
GET/subscriptions/{subscriptionId}/providers/Microsoft.DigitalTwins/digitalTwinsInstances
DigitalTwins_List
POST/subscriptions/{subscriptionId}/providers/Microsoft.DigitalTwins/locations/{location}/checkNameAvailability
DigitalTwins_CheckNameAvailability
GET/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances
DigitalTwins_ListByResourceGroup
GET/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}
DigitalTwins_Get
PUT/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}
DigitalTwins_CreateOrUpdate
DELETE/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}
DigitalTwins_Delete
PATCH/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}
DigitalTwins_Update
GET/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}/endpoints
DigitalTwinsEndpoint_List
GET/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DigitalTwins/digitalTwinsInstances/{resourceName}/endpoints/{endpointName}
DigitalTwinsEndpoint_Get
← View Config URLView AzureDigitalTwinsManagementClientMCP Details →