Update Server
Servers API
Update Server
Update metadata and configuration of an existing MCP server
PUT
Update Server
Documentation Index
Fetch the complete documentation index at: https://acm-aa28ebf6.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint
Authentication
- Required
This endpoint requires authentication. You must be the server owner.
Path Parameters
Unique server identifier to update. Example:
weather-mcpRequest Body
All fields are optional. Only include fields you want to update.
New semantic version number. Format:
MAJOR.MINOR.PATCH. Must be greater than the current version.Updated description. Length: 20-500 characters
Updated software license. Examples:
MIT, Apache-2.0, GPL-3.0Updated repository information
Updated pricing configuration
Pricing changes take effect immediately for new users
Optional metadata updates
Response
"success" on success, "error" on failureHuman-readable confirmation message
The updated server object (same structure as the Get Server response)
Examples
Response Examples
Update Scenarios
Version Bump
Version Bump
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
Pricing Changes
Pricing Changes
Existing users keep their current pricing until the next billing cycle
Description Updates
Description Updates
Repository Migration
Repository Migration
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