Update a client
Changed onEdit a client's display name and/or its config. Two ways to change the config: config replaces it wholesale, and set changes named fields over the config read inside the write transaction — prefer set, because a whole-config round-trip composed from a stale read reverts whatever landed in between.
Config edits require expectedConfigId and renames require expectedName. A stale token is 409 CONFLICT whose details carries the current value: re-read the client and retry. A config edit that resolves to byte-identical settings writes nothing at all.
Guest callers are denied (a write).
Request
- Base URLhttps://app.mcpjam.com/api/v1
- URLhttps://app.mcpjam.com/api/v1/projects/{projectId}/clients/{client}
- AuthHTTP bearer
Path parameters
ID of the hosted project that contains the server.
Client name or ID. A name is matched case-insensitively and must be unique in the project; an ambiguous name is refused with 409 CONFLICT listing the candidate ids rather than resolved to one of them.
Request body
Response
The updated client settings.
Changes
- breaking
removed from the
/request propertyoneOflist - info
added to the
/request propertyoneOflist
- breaking
- info
added the new optional request property
/
- info