Add DELETE method to the OpenAPI specification#782
Merged
Conversation
blkt
reviewed
Nov 18, 2025
Comment on lines
+201
to
+210
| '500': | ||
| description: Internal server error | ||
| content: | ||
| application/json: | ||
| schema: | ||
| type: object | ||
| properties: | ||
| error: | ||
| type: string | ||
| example: "Failed to delete server version" |
There was a problem hiding this comment.
nit: it would be nice to return a 501 Not Implemented in case the server does not support server version deletion.
Member
Author
There was a problem hiding this comment.
Thanks! I also added it to publish since we've missed it there too 👍
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
rdimitrov
force-pushed
the
add-delete
branch
from
9079c18 to
5ac24bf
Compare
Member
Author
Addressed 🚀 |
domdomegg
approved these changes
Nov 19, 2025
Swathi-MuraliSrinivasan
pushed a commit
to Swathi-MuraliSrinivasan/paychex-mcp-registry
that referenced
this pull request
Nov 20, 2025
) <!-- Provide a brief summary of your changes --> ## Motivation and Context <!-- Why is this change needed? What problem does it solve? --> 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? <!-- Have you tested this in a real application? Which scenarios were tested? --> ## Breaking Changes <!-- Will users need to update their code or configurations? --> ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] 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 <!-- Go over all the following points, and put an `x` in all the boxes that apply. --> - [ ] 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 <!-- Add any other context, implementation notes, or design decisions --> --------- Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context