> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hasmcp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What happens when I send a DELETE request to an MCP server endpoint?

> Explanation of the cascade effects and data cleanup that occurs when issuing a DELETE request to a HasMCP server.

# Consequences of a DELETE Request

## Using HasMCP UI

<img src="https://mintcdn.com/hasmcp/d2X-lsG7b5q-dkAh/images/kb/server-delete-confirm.png?fit=max&auto=format&n=d2X-lsG7b5q-dkAh&q=85&s=97e44ace85d258e7d995dc0a17f3261b" alt="Delete MCP Server Confirmation Modal" width="2560" height="1440" data-path="images/kb/server-delete-confirm.png" />

When you attempt to delete a server in the dashboard, the UI warns you about the destructive nature of the action. Clicking **Confirm** triggers the `DELETE` request in the background.

## Using REST API

Sending a `DELETE /servers/{id}` request programmatically is a destructive action that permanently de-provisions your MCP server from the HasMCP Manager.

### Cascade Effects

When the `204 No Content` status is returned:

1. **Server Configuration Removed**: All metadata associated purely with the server (`name`, `instructions`, `version`) is destroyed.
2. **Tokens Revoked**: Any active tokens specifically generated for this MCP server (`ServerToken`) are immediately invalidated and deleted. This protects against unauthorized future access.
3. **Associations Dropped**: Connections mapping this server to `providers`, `tools`, `resources`, and `prompts` are severed.
4. **Underlying Entities Remained Untouched**: Importantly, deleting a server *does not* delete the underlying Provider, Tool, or Prompt configurations from the manager. These exist globally in your workspace and remain fully available to be attached to other active servers.