Update an MCP server.
Every field is optional. Omitting a field leaves its current value unchanged; a full resend of every field is NOT required to update a single field (e.g. PUT { "name": "new name" } only renames the server and leaves url/status/auth_type/api_key_header/secret exactly as they were).
Path parameters
The MCP server ID.
Request body
Example request
{
"status": "active"
}Response
Details of the updated MCP server.
Example response
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"customer_id": "7c4d2f3a-1b8e-4f5c-9a6d-3e2f1a0b4c5d",
"name": "Internal Ticketing System",
"detail": "Exposes ticket lookup/creation tools to the LLM.",
"url": "https://mcp.example.com/mcp",
"status": "active",
"auth_type": "bearer",
"api_key_header": "X-API-Key",
"oauth_vendor": "github",
"has_secret": true,
"tm_create": "2026-01-15T09:30:00.000000Z",
"tm_update": "2026-01-15T09:30:00.000000Z",
"tm_delete": "2026-01-15T09:30:00.000000Z"
}Changes
Changed in 4 of the 97 revisions of this API.14
- ○
added the new
oauthenum value to the request propertyrequest-property-enum-value-added
- ○
- ○
the response property
became required for the statusresponse-property-became-required
- ○
- ●
added the new
oauthenum value to theresponse property for the response statusresponse-property-enum-value-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ●
- ○
endpoint added
endpoint-added
- ○