Delete a custom MCP server
POST/api/v1/mcp-servers/delete
Removes the server record. Deleting an absent server succeeds with deleted: false. Conversations and profiles retain references to the deleted ID, so remove those references separately. New resolution fails once deletion is observed; in-flight calls and previously loaded definitions are not recalled. The referenced secret is left in place.
To retain the configuration while disabling the server, set enabled: false through update.
The following access conditions are preserved as declared intent and are not implemented by generated code: Authorized scoped domain action.
Use this in a guide: Answer questions about a website using your own Firecrawl account
Request
Responses
- 200
Delete processed
Use the unprefixed serverId of a custom server registered in your project.
Section ID: DOC-IN-tools-connections-servers-api-deleteCustomMcpServer#example-mcp-servers-deleteCustomMcpServer-request
Request example
{
"serverId": "product-tools"
}
Illustrative response shape; omitted default fields and actual outcomes depend on the operation.
Section ID: DOC-IN-tools-connections-servers-api-deleteCustomMcpServer#example-mcp-servers-deleteCustomMcpServer-response
Response example
{
"deleted": true
}
Document ID: DOC-IN-tools-connections-servers-api-deleteCustomMcpServer. Section identities and revisions.
| Section | Stable reference |
|---|---|
| Delete a custom MCP server | DOC-IN-tools-connections-servers-api-deleteCustomMcpServer#overview |
| Request | DOC-IN-tools-connections-servers-api-deleteCustomMcpServer#request |
| Responses | DOC-IN-tools-connections-servers-api-deleteCustomMcpServer#responses |