Delete an MCP server registration
DELETE /admin/ai/mcp-clients/{id}
Deletes the registration and all of its tool grants, and answers
204. An id that matches nothing also gets 204, so the 404 isn’t
used.
You need mcp.client.admin or system.admin for the whole install;
a permission held only for a team doesn’t count, and neither does
ai.admin. An id that isn’t a UUID gets a plain-text 400, even
when you aren’t signed in. Otherwise signed-out callers get 401 and
callers without the permission 403.
New tool calls naming the deleted server are refused while no server with that name is registered, and a call already past that check isn’t stopped. If the server was enabled when the app started, the app keeps any client it configured and any health checks it started for it until a restart. Past usage records keep its name. Deleting isn’t recorded in the audit log. Server errors get a plain-text 500.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The registration’s ID. A value that isn’t a UUID gets a plain-text 400.
Responses
Section titled “ Responses ”Deleted, or there was nothing to delete.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Authenticated but missing required capabilities
object
Human-readable error summary
Example
the request could not be completedResource not found
object
Human-readable error summary
Example
the request could not be completed