microsoft/mcp

[ONBOARD] Azure Arc Developer Scenarios

Open

#163 opened on Sep 3, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (560 forks)auto 404
help wantedonboardingserver-Azure.Mcp

Repository metrics

Stars
 (3,498 stars)
PR merge metrics
 (PR metrics pending)

Description

Service / Tool Name

Azure Arc Dev Experiences

Contacts

tonyni@microsoft.com, rosalinswain@microsoft.com, chjosh@microsoft.com

Intended Agent Scenarios

  1. Connect AKS cluster to Arc
  2. Deploy Graytown services like secret sync, ACSA, AIO
  3. Upgrade Arc Agent
  4. Upgrade user services

Timeline

TBD

Contributor guide

Research direction
To implement these scenarios, start by understanding Azure Arc's resource model and API. Look at the existing MCP server codebase to see how it currently handles connections and services. For each scenario, identify the Arc REST API calls needed and map them to MCP tool definitions.
Tech stack
csharp
Domain
infrastructuredevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
AzureKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30