From 313457571244a3469e55dc108a6a100bb0d3e27b Mon Sep 17 00:00:00 2001 From: Radoslav Dimitrov Date: Wed, 19 Nov 2025 17:15:49 +0200 Subject: [PATCH] Add DELETE method to the OpenAPI specification (#782) ## Motivation and Context The following adds a DELETE method to the reference API specification of the registry. The endpoint is consistent with the rest of the spec and provides a standardised way for registry implementations to support deletion if they choose to. **Details:** * Endpoint: DELETE /v0/servers/{serverName}/versions/{version} * Uses tags: [publish] (same as POST /v0/publish for write operations) * Requires security: bearerAuth authentication * Returns ServerResponse on success (200) - matching POST pattern * Same error responses: 401 (Unauthorized), 403 (Forbidden), 500 (Internal error) * Added 404 (Not Found) for when server/version doesn't exist * Parameters match the GET endpoint format with URL-encoding examples * Marked as "(Optional)" in summary * Explicit note that it's not implemented by the official registry * States it's included for standardization purposes ## 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](https://modelcontextprotocol.io) - [ ] 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 --- docs/reference/api/generic-registry-api.md | 1 + docs/reference/api/openapi.yaml | 93 ++++++++++++++++++++++ 2 files changed, 94 insertions(+) diff --git a/docs/reference/api/generic-registry-api.md b/docs/reference/api/generic-registry-api.md index 3f8cd65..614eb81 100644 --- a/docs/reference/api/generic-registry-api.md +++ b/docs/reference/api/generic-registry-api.md @@ -18,6 +18,7 @@ The official registry has some more endpoints and restrictions on top of this. S - **`GET /v0/servers/{serverName}/versions`** - List all versions of a server - **`GET /v0/servers/{serverName}/versions/{version}`** - Get specific version of server. Use the special version `latest` to get the latest version. - **`POST /v0/publish`** - Publish new server (optional, registry-specific authentication) +- **`DELETE /v0/servers/{serverName}/versions/{version}`** - Delete specific server version (optional, not implemented by official registry) Server names and version strings should be URL-encoded in paths. diff --git a/docs/reference/api/openapi.yaml b/docs/reference/api/openapi.yaml index a661a87..1e8a842 100644 --- a/docs/reference/api/openapi.yaml +++ b/docs/reference/api/openapi.yaml @@ -135,6 +135,89 @@ paths: error: type: string example: "Server not found" + delete: + tags: [publish] + summary: Delete specific MCP server version (Optional) + description: | + Delete a specific version of an MCP server from the registry. + + **Note**: This endpoint is optional for registry implementations and is not implemented by the official MCP registry. It is included in the specification to standardize the deletion mechanism for registry implementations that choose to support it. + + Authentication mechanism is registry-specific and may vary between implementations. + security: + - bearerAuth: [] + parameters: + - name: serverName + in: path + required: true + description: URL-encoded server name (e.g., "com.example%2Fmy-server") + schema: + type: string + example: "com.example%2Fmy-server" + - name: version + in: path + required: true + description: URL-encoded version to delete (e.g., "1.0.0" or "1.0.0%2B20130313144700" for versions with build metadata) + schema: + type: string + example: "1.0.0" + responses: + '200': + description: Successfully deleted server version + content: + application/json: + schema: + $ref: '#/components/schemas/ServerResponse' + '401': + description: Unauthorized - Invalid or missing authentication token + content: + application/json: + schema: + type: object + properties: + error: + type: string + example: "Invalid or expired Registry JWT token" + '403': + description: Forbidden - Insufficient permissions + content: + application/json: + schema: + type: object + properties: + error: + type: string + example: "You do not have permission to delete this server" + '404': + description: Server or version not found + content: + application/json: + schema: + type: object + properties: + error: + type: string + example: "Server version not found" + '500': + description: Internal server error + content: + application/json: + schema: + type: object + properties: + error: + type: string + example: "Failed to delete server version" + '501': + description: Not Implemented - Registry does not support deletion + content: + application/json: + schema: + type: object + properties: + error: + type: string + example: "Deletion is not supported by this registry" /v0/publish: post: tags: [publish] @@ -239,6 +322,16 @@ paths: error: type: string example: "Failed to publish server" + '501': + description: Not Implemented - Registry does not support publishing + content: + application/json: + schema: + type: object + properties: + error: + type: string + example: "Publishing is not supported by this registry" components: securitySchemes: bearerAuth: