Skip to main content
PUT
Update Server

Endpoint

Authentication

This endpoint requires authentication. You must be the server owner.
Only the server owner can update server metadata

Path Parameters

string
required
Unique server identifier to update. Example: weather-mcp

Request Body

All fields are optional. Only include fields you want to update.
string
New semantic version number. Format: MAJOR.MINOR.PATCH. Must be greater than the current version.
string
Updated description. Length: 20-500 characters
string
Updated software license. Examples: MIT, Apache-2.0, GPL-3.0
object
Updated repository information
Changing the repository URL will trigger a new security scan
object
Updated pricing configuration
Pricing changes take effect immediately for new users
object
Optional metadata updates

Response

string
"success" on success, "error" on failure
string
Human-readable confirmation message
object
The updated server object (same structure as the Get Server response)

Examples

Response Examples

Update Scenarios

When to bump versions:
  • Patch (1.0.0 to 1.0.1): Bug fixes, minor changes
  • Minor (1.0.0 to 1.1.0): New features, backward compatible
  • Major (1.0.0 to 2.0.0): Breaking changes
Existing users keep their current pricing until the next billing cycle
Repository changes trigger a new security scan

Best Practices

Semantic Versioning

Follow semver strictly to communicate changes clearly to users

Document Changes

Update your README and changelog when making updates

Test Before Update

Test changes in your repository before updating the server

Notify Users

For breaking changes, notify users through your communication channels