Update a custom MCP server
POST/api/v1/mcp-servers/update
Replaces the mutable server configuration and increments its version. Read the
saved record, edit the intended fields and submit the complete desired server:
omitting enabled disables it,
and omitted optional fields are cleared. The top-level serverId selects the
record; an update cannot rename it. There is no revision precondition, so concurrent
stale updates can overwrite one another.
A saved update does not confirm that every subsequent call has switched to the
new configuration, and it does not cancel in-flight calls. Use get to inspect the
saved record and test-connection to check a connection using it. The same
validation as create applies; an unknown server returns 404.
Request
Responses
- 200
Server updated; the stored record is echoed back
Document ID: DOC-IN-tools-connections-servers-api-updateCustomMcpServer. Section identities and revisions.
| Section | Stable reference |
|---|---|
| Overview | DOC-IN-tools-connections-servers-api-updateCustomMcpServer#overview |
| Request | DOC-IN-tools-connections-servers-api-updateCustomMcpServer#request |
| Responses | DOC-IN-tools-connections-servers-api-updateCustomMcpServer#responses |