Skip to content

Conversation

@joelverhagen
Copy link
Contributor

@joelverhagen joelverhagen commented Oct 23, 2025

What does this PR do?

The MCP Registry has iterated the schema version two more times, and has now locked it as a "v0.1". Fortunately this new schema version does not actually impact us but the MCP Registry does assert the new schema URL.

See https://github.com/modelcontextprotocol/registry/blob/main/docs/reference/server-json/CHANGELOG.md

Related PR for the mcpserver template package: dotnet/extensions#6956

GitHub issue number?

#870

Pre-merge Checklist

  • Required for All PRs
    • Read contribution guidelines
    • PR title clearly describes the change
    • Commit history is clean with descriptive messages (cleanup guide)
    • Added comprehensive tests for new/modified functionality N/A
    • Updated servers/Azure.Mcp.Server/CHANGELOG.md and/or servers/Fabric.Mcp.Server/CHANGELOG.md for product changes (features, bug fixes, UI/UX, updated dependencies)
  • For MCP tool changes:
    • One tool per PR: This PR adds or modifies only one MCP tool for faster review cycles
    • Updated servers/Azure.Mcp.Server/README.md and/or servers/Fabric.Mcp.Server/README.md documentation
    • Validate README.md changes using script at eng/scripts/Process-PackageReadMe.ps1. See Package README
    • Updated command list in /servers/Azure.Mcp.Server/docs/azmcp-commands.md and/or /docs/fabric-commands.md
    • Run .\eng\scripts\Update-AzCommandsMetadata.ps1 to update tool metadata in azmcp-commands.md (required for CI)
    • For new or modified tool descriptions, ran ToolDescriptionEvaluator and obtained a score of 0.4 or more and a top 3 ranking for all related test prompts
    • For new tools associated with Azure services or publicly available tools/APIs/products, add URL to documentation in the PR description
  • Extra steps for Azure MCP Server tool changes:
    • Updated test prompts in /servers/Azure.Mcp.Server/docs/e2eTestPrompts.md
    • 👉 For Community (non-Microsoft team member) PRs:
      • Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (crypto mining, spam, data exfiltration, etc.)
      • Manual tests run: added comment /azp run mcp - pullrequest - live to run Live Test Pipeline

Copilot AI review requested due to automatic review settings October 23, 2025 21:36
@joelverhagen joelverhagen requested review from a team as code owners October 23, 2025 21:36
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 updates the MCP schema version reference from 2025-09-29 to 2025-10-17 across server configuration files to align with the latest MCP Registry v0.1 schema. The schema URL update is a metadata change that does not affect functionality but ensures compatibility with the MCP Registry's assertions.

  • Updates schema version in PowerShell packaging script
  • Updates schema version in DNX server configuration template
  • Documents the schema version update in the Azure MCP Server changelog

Reviewed Changes

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

File Description
servers/Azure.Mcp.Server/CHANGELOG.md Documents the schema version update in the unreleased changes section
eng/scripts/Pack-Nuget.ps1 Updates the $schema URL in the NuGet package server.json generation function
eng/dnx/.mcp/server.json Updates the $schema URL in the DNX server configuration template

@joshfree joshfree added this to the 2025-11 milestone Oct 27, 2025
@joshfree joshfree moved this from Untriaged to In Progress in Azure MCP Server Oct 27, 2025
@joshfree
Copy link
Member

@chidozieononiwu PTAL

@joelverhagen joelverhagen requested a review from a team as a code owner October 29, 2025 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants