Add or Replace an MCP Tool
Record a tool definition on an MCP server.
POST
Upsert an MCP tool row
Creates the tool row, or replaces it if one with the same name already exists.
Recording a tool here does not by itself expose it. A tool is reachable only when
it is also in the server’s
allowed_tools — the allowlist is the control, and
this endpoint is the catalogue.
Requires the update capability on ai_gateway. See the control-plane overview for authentication, the {data, meta} envelope, pagination and error types.Authorizations
OAuth 2.1 authentication — recommended for new integrations. Access tokens
(kc_ prefix) are minted at the root-host token endpoint
https://api.knoxcall.com/oauth/token and passed as Authorization: Bearer <access_token>.
Public clients must use PKCE with the authorization_code grant; confidential
clients may use client_credentials. The first-party SDKs and the
knoxcall login CLI handle token minting, caching, refresh, and DPoP for you.
Path Parameters
The MCP server UUID.
Body
application/json