-
Notifications
You must be signed in to change notification settings - Fork 4.1k
[MCP] PR Patches (sync to main) #28704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Added a temporary edit comment in the cleanupEnv function.
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this 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 |
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.