[MCP] Async -> Sync Execution for server commands.

[notyashhh]

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.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• 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

[azure-client-tools-bot-prd]

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

[Copilot]

Pull Request Overview

This PR introduces a new Model Context Protocol (MCP) server under tools/Mcp to support synchronous execution of server commands for Azure PowerShell code generation using AutoRest.

• Sets up the TypeScript project (tsconfig.json, package.json) and adds necessary dependencies.
• Implements the core MCP server (CodegenServer.ts, index.ts) with tool registration based on JSON specs.
• Adds utility functions (utils.ts), tool service handlers (toolServices.ts), and tool specifications/responses (specs.json, responses.json).

Reviewed Changes

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

Show a summary per file

File	Description
tools/Mcp/tsconfig.json	Configures compiler options for the TypeScript project.
tools/Mcp/package.json	Defines project metadata, dependencies, and build scripts.
tools/Mcp/src/CodegenServer.ts	Implements MCP server initialization and tool registration.
tools/Mcp/src/index.ts	Entry point that starts and connects the MCP server.
tools/Mcp/src/services/utils.ts	Provides file, YAML, and HTTP utilities for tool operations.
tools/Mcp/src/services/toolServices.ts	Contains implementations of MCP tool handlers.
tools/Mcp/src/specs/specs.json	Defines tool schemas and callback names used by the server.
tools/Mcp/src/specs/responses.json	Provides response templates for each tool.
tools/Mcp/src/types.ts	Declares TypeScript types for schemas and directives.
tools/Mcp/README.md	Documents installation, usage, and features of the MCP server.

Files not reviewed (1)

• tools/Mcp/package-lock.json: Language not supported

Comments suppressed due to low confidence (7)

tools/Mcp/src/services/utils.ts:7

• [nitpick] The parameter name path shadows the imported path module. Consider renaming it to directory or cwd to avoid confusion.

const _pwshCD = (path: string): string => { return `pwsh -Command "$path = resolve-path ${path} | Set-Location"` }

tools/Mcp/src/specs/responses.json:24

• Spelling error: "Fulfil" should be "Fulfill".

        "type": "tool",

tools/Mcp/src/services/utils.ts:24

• There's an extraneous trailing double quote at the end of the command string, which will break execution. Remove the final ".

    const genBuildCommand = `${_pwshCD(workingDirectory)}; ${_autorest}; ${_pwshBuild};"`;

tools/Mcp/src/services/utils.ts:11

• The testYaml function appears to be a leftover utility and is not used elsewhere. Consider removing it or moving it to a dedicated test file.

function testYaml() {

tools/Mcp/src/services/utils.ts:197

• The testCase function is hardcoded to a local path and unused. Remove it or refactor it into a proper test suite.

export async function testCase() {

tools/Mcp/src/services/toolServices.ts:5

• The get import from 'http' is unused. Consider removing this import.

import { get } from 'http';

tools/Mcp/src/CodegenServer.ts:106

• Typo in the description: "such a formal" should read "such as formal" for clarity.

            { name: z.string().describe("Name of the person to greet"), style: z.string().describe("The style of greeting, such a formal, excited, or casual. If not specified casual will be used")},