ApiMCP Servers

Delete an MCP server

DELETE
/mcp-servers/{id}

Delete an MCP server and its stored headers. Deletion is refused with HTTP 409 while an assistant still uses the server, so no assistant loses a tool as a side effect. Remove the mcp tool from those assistants first.

Authorization

BearerAuth
AuthorizationBearer <token>

API key authentication. Get your key from the dashboard.

In: header

Path Parameters

id*string

MCP server UUID

Formatuuid

Response Body

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/mcp-servers/497f6eca-6276-4993-bfeb-53cbbbba6f08"
{
  "success": true
}
{
  "error": "Invalid API key",
  "message": "string"
}
{
  "error": "Invalid API key",
  "message": "string"
}
{
  "error": "MCP server is used by 2 assistants (Reception, After hours). Remove the mcp tool from those assistants first.",
  "assistants": [
    {
      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
      "name": "string"
    }
  ]
}

Update an MCP server PATCH

Change an MCP server. Only the fields you send are changed. `headers` replaces all stored headers: leave it out to keep them, send `{}` to remove them. Use this to renew a token that expires. When `url` points to a different host (scheme, host or port) than before, send `headers` in the same request, `{}` if the new host needs none: stored headers never go to a new host, and without them the request is refused with 400. The change applies from the next call; calls in progress keep the connection they opened.

Test an MCP server POST

Connect to the MCP server from the platform and list its tools, with the stored headers. Use it after adding a server, and to see the exact tool names for `allowed_tools`. To test a token you only pass per call, send it in `headers`: those are merged over the stored headers for this test only and are not stored.