Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Enables managing Azure Service Fabric Managed Clusters through the Azure REST API, supporting create, read, update, delete, and list operations.

README.md

Service Fabric Managed Clusters MCP Server

An MCP (Model Context Protocol) server for managing Azure Service Fabric Managed Clusters through the Azure REST API.

Features

This MCP server provides tools to:

  • Create Service Fabric managed clusters
  • Read cluster information (get by name, list by resource group or subscription)
  • Update existing clusters (tags, configuration, version upgrades)
  • Delete managed clusters
  • Azure Authentication: Supports multiple Azure authentication methods (CLI, Service Principal, Managed Identity)
  • Type Safety: Full TypeScript support with Zod validation

Prerequisites

  • Node.js 18 or later
  • An Azure subscription
  • Azure authentication credentials (one of the following):
  • Azure CLI logged in (az login)
  • Service Principal credentials (tenant ID, client ID, client secret)
  • Managed Identity (when running on Azure)

Installation

cd mcp-server-template
npm install
npm run build

Authentication

This server uses Azure Identity libraries and supports multiple authentication methods:

Option 1: Azure CLI (Easiest for local development)

az login

Option 2: Service Principal

# Set environment variables
export AZURE_TENANT_ID="your-tenant-id"
export AZURE_CLIENT_ID="your-client-id"
export AZURE_CLIENT_SECRET="your-client-secret"

Or pass them as command-line arguments (see Usage below).

Option 3: Managed Identity

When running on Azure (VM, App Service, etc.), the server will automatically use the managed identity.

Usage

Basic Usage with Azure CLI Authentication

node dist/index.js --subscription-id "your-subscription-id"

Usage with Service Principal

node dist/index.js \
  --subscription-id "your-subscription-id" \
  --tenant-id "your-tenant-id" \
  --client-id "your-client-id" \
  --client-secret "your-client-secret"

Command-Line Options

| Option | Alias | Description | Required | |--------|-------|-------------|----------| | --subscription-id | -s | Azure subscription ID | Yes | | --tenant-id | -t | Azure tenant ID | No | | --client-id | -c | Service principal client ID | No | | --client-secret | - | Service principal client secret | No* | | --domains | -d | Domains to enable (default: sfmc) | No | | --help | - | Show help | No | | --version | - | Show version | No |

\* Required only if using Service Principal authentication

Using with MCP Inspector

For testing and debugging, use the MCP Inspector:

npm run inspect

Then interact with the server at http://localhost:5173.

IDE Integration

VS Code Integration

For VS Code setup, see the detailed guide: VSCODE_SETUP.md

Quick Setup: Create or edit .vscode/settings.json in your workspace:

{
  "mcp.servers": {
    "service-fabric": {
      "command": "node",
      "args": [
        "${workspaceFolder}/dist/index.js",
        "--subscription-id",
        "your-subscription-id"
      ]
    }
  }
}

A template is provided at .vscode/settings.json.example.

Claude Desktop Integration

Add this configuration to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "service-fabric": {
      "command": "node",
      "args": [
        "/path/to/mcp-server-template/dist/index.js",
        "--subscription-id",
        "your-subscription-id"
      ],
      "env": {
        "AZURE_TENANT_ID": "your-tenant-id",
        "AZURE_CLIENT_ID": "your-client-id",
        "AZURE_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Or if using Azure CLI authentication:

{
  "mcpServers": {
    "service-fabric": {
      "command": "node",
      "args": [
        "/path/to/mcp-server-template/dist/index.js",
        "--subscription-id",
        "your-subscription-id"
      ]
    }
  }
}

Available Tools

1. sfmc_create_cluster

Creates or updates a Service Fabric managed cluster.

Parameters:

  • resourceGroupName (string, required): The resource group name
  • clusterName (string, required): The cluster name
  • location (string, required): Azure region (e.g., "eastus", "westeurope")
  • dnsName (string, required): The cluster's DNS name
  • adminUserName (string, optional): VM admin username
  • adminPassword (string, optional): VM admin password
  • sku (string, optional): Cluster SKU - "Basic" or "Standard" (default: "Basic")
  • clientConnectionPort (number, optional): Client connection port (default: 19000)
  • httpGatewayConnectionPort (number, optional): HTTP gateway port (default: 19080)
  • clusterCodeVersion (string, optional): Service Fabric runtime version
  • tags (object, optional): Resource tags
  • apiVersion (string, optional): API version (default: "2024-11-01-preview")

Example: ``json { "resourceGroupName": "my-rg", "clusterName": "my-cluster", "location": "eastus", "dnsName": "mycluster", "sku": "Standard", "adminUserName": "adminuser", "adminPassword": "P@ssw0rd123!", "tags": { "environment": "production", "owner": "team-a" } } ``

2. sfmc_get_cluster

Retrieves information about a specific managed cluster.

Parameters:

  • resourceGroupName (string, required): The resource group name
  • clusterName (string, required): The cluster name
  • apiVersion (string, optional): API version (default: "2024-11-01-preview")

Example: ``json { "resourceGroupName": "my-rg", "clusterName": "my-cluster" } ``

3. sfmc_update_cluster

Updates an existing managed cluster (partial update).

Parameters:

  • resourceGroupName (string, required): The resource group name
  • clusterName (string, required): The cluster name
  • tags (object, optional): Updated resource tags
  • clusterCodeVersion (string, optional): Service Fabric version to upgrade to
  • clientConnectionPort (number, optional): Updated client connection port
  • httpGatewayConnectionPort (number, optional): Updated HTTP gateway port
  • apiVersion (string, optional): API version (default: "2024-11-01-preview")

Example: ``json { "resourceGroupName": "my-rg", "clusterName": "my-cluster", "clusterCodeVersion": "9.1.1583.9590", "tags": { "environment": "staging" } } ``

4. sfmc_delete_cluster

Deletes a managed cluster (long-running operation).

Parameters:

  • resourceGroupName (string, required): The resource group name
  • clusterName (string, required): The cluster name to delete
  • apiVersion (string, optional): API version (default: "2024-11-01-preview")

Example: ``json { "resourceGroupName": "my-rg", "clusterName": "my-cluster" } ``

5. sfmc_list_clusters

Lists all managed clusters in a resource group.

Parameters:

  • resourceGroupName (string, required): The resource group name
  • apiVersion (string, optional): API version (default: "2024-11-01-preview")

Example: ``json { "resourceGroupName": "my-rg" } ``

6. sfmc_list_clusters_by_subscription

Lists all managed clusters in the subscription.

Parameters:

  • apiVersion (string, optional): API version (default: "2024-11-01-preview")

Example: ``json { "apiVersion": "2024-11-01-preview" } ``

Development

Build

npm run build

Watch Mode

npm run watch

Format Code

npm run format

Lint

npm run lint

Clean Build Artifacts

npm run clean

API Reference

This MCP server is based on the Azure Service Fabric Managed Clusters REST API:

https://learn.microsoft.com/en-us/rest/api/servicefabric/managedclusters/managed-clusters?view=rest-servicefabric-managedclusters-2024-11-01-preview

Troubleshooting

Authentication Errors

If you see authentication errors:

  1. Check Azure CLI login:
   az login
   az account show
  1. Verify service principal credentials:
   az login --service-principal \
     --username $AZURE_CLIENT_ID \
     --password $AZURE_CLIENT_SECRET \
     --tenant $AZURE_TENANT_ID
  1. Check subscription access:
   az account set --subscription "your-subscription-id"
   az account show

Common Errors

  • "subscriptionId is required": Make sure to pass --subscription-id argument
  • "401 Unauthorized": Check your Azure credentials
  • "403 Forbidden": Verify you have appropriate RBAC permissions on the subscription/resource group
  • "404 Not Found": The cluster or resource group doesn't exist
  • "409 Conflict": The cluster is currently being modified by another operation

License

MIT

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Cloud & DevOps servers.