Update an MCP server

PATCH

mcp-servers

{id}

curl -X PATCH "https://api.nedzo.ai/v1/mcp-servers/9b2f6c1a-3e4d-4a5b-8c7d-0e1f2a3b4c5d" \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{ "name": "Inventory" }'

{
  "id": "9b2f6c1a-3e4d-4a5b-8c7d-0e1f2a3b4c5d",
  "workspaceId": "789e4567-e89b-12d3-a456-426614174000",
  "name": "Inventory",
  "url": "https://mcp.example.com/mcp",
  "authType": "bearer",
  "hasAuth": true,
  "headerNames": [],
  "toolCount": 4,
  "lastConnectedAt": "2026-10-11T10:00:00Z",
  "createdAt": "2026-10-11T09:00:00Z",
  "updatedAt": "2026-10-11T10:00:00Z"
}

This endpoint is for the VIP plan only. Other plans get a 403. See Plan access.

Send only the fields to change.

Path Parameters

string

required

MCP server UUID

Body

string

The server’s name, up to 255 characters. Each name is used once per workspace.

string

The server URL, up to 2,048 characters. It must be a public https address. Each URL is used once per workspace.

string

bearer or api_key. Send null to remove the auth.

string

The secret for authType, up to 4,096 characters. Required when you set authType on a server that has no saved auth.

object

Extra headers to send. Up to 10 headers, each value up to 1,024 characters. You can’t set Host, Content-Length, Transfer-Encoding, Connection, Authorization or Content-Type. Use authType and authValue for auth.

authValue and header values are write only. We never send them back. A response shows hasAuth and the header names.

If you change url to another address (a different host, http or https, or port), send authValue and headers again in the same request, or set authType to null and headers to {} to remove them. The saved ones stay with the old address, and we refuse the change with a 400.

curl -X PATCH "https://api.nedzo.ai/v1/mcp-servers/9b2f6c1a-3e4d-4a5b-8c7d-0e1f2a3b4c5d" \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{ "name": "Inventory" }'

{
  "id": "9b2f6c1a-3e4d-4a5b-8c7d-0e1f2a3b4c5d",
  "workspaceId": "789e4567-e89b-12d3-a456-426614174000",
  "name": "Inventory",
  "url": "https://mcp.example.com/mcp",
  "authType": "bearer",
  "hasAuth": true,
  "headerNames": [],
  "toolCount": 4,
  "lastConnectedAt": "2026-10-11T10:00:00Z",
  "createdAt": "2026-10-11T09:00:00Z",
  "updatedAt": "2026-10-11T10:00:00Z"
}

Errors

Status	When
`400`	A field is wrong, the URL is not a public `https` address, or `url` moved to another address without the auth and headers.
`400`	`authValue is required when setting authType on a server without existing credentials`.
`400`	More than 10 headers, or a header you can’t set. The `detail` is `Invalid request body`, and the `errors` entry for `headers` has the message `Maximum 10 custom headers allowed` or `Blocked header name detected`.
`400`	`An MCP server with this name already exists in your workspace`, or the same with `URL`.
`404`	The server is not in your API key’s scope.

curl -X PATCH "https://api.nedzo.ai/v1/mcp-servers/9b2f6c1a-3e4d-4a5b-8c7d-0e1f2a3b4c5d" \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{ "name": "Inventory" }'

{
  "id": "9b2f6c1a-3e4d-4a5b-8c7d-0e1f2a3b4c5d",
  "workspaceId": "789e4567-e89b-12d3-a456-426614174000",
  "name": "Inventory",
  "url": "https://mcp.example.com/mcp",
  "authType": "bearer",
  "hasAuth": true,
  "headerNames": [],
  "toolCount": 4,
  "lastConnectedAt": "2026-10-11T10:00:00Z",
  "createdAt": "2026-10-11T09:00:00Z",
  "updatedAt": "2026-10-11T10:00:00Z"
}

API Reference

Workspaces

Agents

Phone Numbers

Contacts

Knowledge

Templates

Campaigns

Workflows

Conversations

Update an MCP server

Path Parameters

Body

Errors