Skip to content

Conversation

@notyashhh
Copy link
Member

Description

Mandatory Checklist

  • SHOULD update ChangeLog.md file(s) appropriately
    • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
      • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT adjust version of module manually in pull request

@Copilot Copilot AI review requested due to automatic review settings October 16, 2025 01:09
@azure-client-tools-bot-prd
Copy link

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

@notyashhh notyashhh changed the base branch from main to dev/mcp-server October 16, 2025 01:09
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR implements a Model Context Protocol (MCP) server for Azure PowerShell code generation workflows, introducing comprehensive tools for scaffolding, generating, and testing Azure PowerShell modules via AutoRest.

  • Adds a new MCP server structure with TypeScript source code, configuration, and build system
  • Implements 7 specialized tools for Azure PowerShell module development workflow
  • Provides automated partner module workflow from service selection to test generation

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

Show a summary per file
File Description
tools/Mcp/tsconfig.json TypeScript compiler configuration for ES2022/Node18 modules
tools/Mcp/test/README.md Test configuration file containing AutoRest directives and Azure API specifications
tools/Mcp/src/types.ts Core TypeScript interfaces for tool parameters, schemas, and responses
tools/Mcp/src/specs/specs.json Tool specifications defining 7 Azure PowerShell workflow tools
tools/Mcp/src/specs/responses.json Response templates mapping tools to instruction files
tools/Mcp/src/services/utils.ts Utility functions for AutoRest operations, GitHub API interactions, and file processing
tools/Mcp/src/services/toolsService.ts Main service implementing tool callbacks and parameter validation
tools/Mcp/src/services/resourcesService.ts Service for handling MCP resources like README templates
tools/Mcp/src/services/promptsService.ts Service for managing workflow prompts and parameter processing
tools/Mcp/src/services/logger.ts Structured logging service with daily rotation and JSON output support
tools/Mcp/src/index.ts Application entry point initializing the MCP server
tools/Mcp/src/assets/test-instructions.md LLM instructions for generating CRUD test cases from help documentation
tools/Mcp/src/assets/partner-module-workflow.md Complete workflow instructions for partner Azure PowerShell module creation
tools/Mcp/src/assets/ideal-modules/Databricks/* Reference examples and tests from the Databricks module for style guidance
tools/Mcp/src/assets/example-instructions.md LLM instructions for generating PowerShell examples from swagger specifications
tools/Mcp/src/assets/autorest-readme-template.md Template for AutoRest README.md configuration files
tools/Mcp/src/CodegenServer.ts Core MCP server implementation with tool, prompt, and resource registration
tools/Mcp/package.json Node.js package configuration with MCP SDK and build dependencies
tools/Mcp/README.md Comprehensive documentation covering installation, usage, and workflow integration

@isra-fel isra-fel merged commit 96df020 into dev/mcp-server Oct 16, 2025
12 checks passed
@isra-fel isra-fel deleted the yash/mcp-patch branch October 16, 2025 01:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants