What problem does it solve?
Adding a new tool to the Azure MCP server involves many coordinated steps—options classes, service implementations, command registration, JSON serialization contexts, unit tests, live test resources, and security validation. This Skill provides a gated, phase-by-phase workflow so nothing is missed and every contribution meets the repository's security and engineering standards.
Core Features & Use Cases
- Phased Implementation Workflow: Walks through toolset scaffolding (Phase 0), command implementation (Phase 1), unit tests (Phase 2), and PR submission, with explicit gates that must pass before proceeding.
- Security-First Guidance: Enforces input validation per Azure resource naming rules, safe logging practices (never logging option objects), endpoint validation via EndpointValidator, and MCP-specific threat mitigations.
- Code Patterns & Templates: Provides ready-to-adapt C# templates for Options classes, SubscriptionCommand implementations, service layers with sovereign cloud support, and JSON serialization contexts.
- Use Case: A developer wants to add a "storage container delete" command to the Azure MCP server. The Skill guides them through creating the options class, implementing the service with proper endpoint validation, writing the command with CommandMetadata attributes, adding unit tests, and verifying the build gates pass.
Quick Start
Ask the AI to add a new Azure MCP tool, for example by describing the command you want such as adding a storage container delete command or creating a new KeyVault toolset with a secret get command.
