Delete servers

Deregisters one of the caller org's external MCP servers, so its tools leave the registry.

DELETE /v1/tool/mcp/servers/{id}

Tool → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/tool/mcp/servers/{id}`
Method	`DELETE`
Operation	`delete_tool_mcp_servers_by_id`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Deregisters one of the caller org's external MCP servers, so its tools leave the registry. Scoped to the caller's org, so an id belonging to another tenant is a 404 and not a delete. Answers 204 with no body; a server this org does not have is 404. Like registering one it takes an admin of the org or a SuperAdmin, and is on the org's audit trail before it is made.

Request

1 field.

Field	In	Type	Required	Description
`id`	path	string	yes	ID is the server to deregister, from the path.

Response

Status	Body	Meaning
`204`	—	no content
`default`	problem-details	refused

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo tool mcp servers rm <id>

.ts

.py

.go

.rs

.java

import { Configuration, ToolApi } from 'hanzoai';

const api = new ToolApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteToolMcpServersById({ id: 'id' });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ToolApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ToolApi(client).delete_tool_mcp_servers_by_id(id='id')

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ToolAPI.DeleteToolMcpServersById(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, tool_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = tool_api::delete_tool_mcp_servers_by_id(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ToolApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new ToolApi(client).deleteToolMcpServersById();

curl -X DELETE https://api.hanzo.ai/v1/tool/mcp/servers/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches tool through the tool tool, which names its 17 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_tools"
         }
       }
     }'

Tool API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousReplace template NextDelete authored