---
title: "[Beta] Delete an McpConfig."
method: POST
path: "/v1/mcp-configs/{id}/delete"
tags: ["mcp-configs"]
---

# [Beta] Delete an McpConfig.

`POST /v1/mcp-configs/{id}/delete`

[Beta] Delete an existing McpConfig. This action is irreversible.

## Path parameters

- `id` string, required

## Request body

- EmptyRecord

## Response `200`

McpConfig deleted successfully.

- McpConfigView — An McpConfig defines a configuration for connecting to an upstream MCP (Model Context Protocol) server. It specifies the target endpoint and which tools are allowed.
  - `id` string, required — The unique identifier of the McpConfig.
  - `name` string, required — The human-readable name of the McpConfig. Unique per account.
  - `endpoint` string, required — The target MCP server endpoint URL (e.g., 'https://mcp.example.com').
  - `allowed_tools` string[], required — Glob patterns specifying which tools are allowed from this MCP server (e.g., ['github.search_*', 'github.get_*'] or ['*'] for all tools).
  - `description` string, nullable — Optional description for this MCP configuration.
  - `create_time_ms` integer, required — Creation time of the McpConfig (Unix timestamp in milliseconds).

## Other responses

- `400` — Bad request. Config is in use by active devboxes.
- `401` — Unauthorized. Invalid or missing authentication.
- `403` — Forbidden. Account does not have devbox capability.
- `404` — McpConfig not found.
- `500` — Internal server error.

## Changes

- **2026-02-05** `15b7fd06098d` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/runloopai/apis/runloop-api/changes/v1/mcp-configs/:id/delete/post.md)

---

[API](https://skmtc.dev/runloopai/apis/runloop-api.md) · [All operations](https://skmtc.dev/runloopai/apis/runloop-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/runloopai/runloop-api/revisions/078a027e147f/schema)