Skip to content

Conversation

@rdimitrov
Copy link
Member

Motivation and Context

The following PR adds a PUT method for updating a server version (optional, not implemented by the registry but still provides the ability for other registry implementations to standardise on it)

Details:

  • Path: PUT /v0.1/servers/{serverName}/versions/{version}
  • Purpose: Update a specific version of an MCP server in the registry
  • Authentication: Uses bearer token authentication (registry-specific)
  • Request Body: Accepts a ServerDetail schema
  • Response: Returns a ServerResponse on success (200)
  • Error Handling: Includes proper HTTP status codes:
    • 401: Unauthorized
    • 403: Forbidden - Insufficient permissions
    • 404: Server or version not found
    • 500: Internal server error
    • 501: Not Implemented - Registry doesn't support updates

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
@rdimitrov rdimitrov requested a review from a team December 10, 2025 22:41
@rdimitrov rdimitrov enabled auto-merge (squash) December 11, 2025 23:44
@rdimitrov rdimitrov merged commit 9357e76 into main Dec 12, 2025
5 checks passed
@rdimitrov rdimitrov deleted the support-update branch December 12, 2025 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants