Syndai Docs

Update a custom tool

PATCH
/api/v1/external/coding/tools/{tool_id}

Edit a tool; a changed config is scanned again. Omitting an MCP server's token keeps the stored one, but moving the server to a new origin requires the token again. Returns 404 for an unknown tool. Requires the coding:tools:write scope.

Authorization

CustomerApiKey
headerAuthorizationBearer <API Key>

Customer API key sent as a bearer token

Path Parameters

tool_id*string
Formatuuid

Query Parameters

customer_id?|null

Request Body

application/json
  1. body
auth_mode?|
Value in"oauth""token""none"null
config?|null
description?string|null
enabled?boolean|null
manual_client?|null
name?string|null
repository_id?|null

Response Body

Request fulfilled, document follows

application/json
  1. response
tool*
Example Request
curl -X PATCH 'https://api.syndai.ai/api/v1/external/coding/tools/497f6eca-6276-4993-bfeb-53cbbbba6f08' \  -H 'Content-Type: application/json' \  -d '{}'
Example Response
{  "tool": {    "auth_mode": "oauth",    "auth_status": "pending",    "config": {},    "description": "string",    "description_hint": "string",    "enabled": true,    "has_token": true,    "id": "string",    "kind": "mcp_server",    "name": "string",    "not_ready_reason": "string",    "oauth": {      "connected_at": "string",      "connected_by_left": true,      "connected_by_name": "string",      "issuer_host": "string",      "redirect_uri": "string",      "requested_scopes": [        "string"      ],      "scopes": [        "string"      ]    },    "repository_id": "string",    "run_ready": true,    "scan_reason": "string",    "scan_status": "scanned",    "scanned_at": "string"  }}