update_mcp_integration
Updates an MCP integration’s URL, auth, headers, tags, or secret mappings; changes apply immediately, so inspect the integration before altering connectivity-related fields.
Instructions
Update an MCP integration's name, description, tags, URL, auth, transport, headers, or runtime Secret Reference mappings. Only supplied fields change; URL, auth, header, and secret changes apply immediately and can break active clients, so inspect get_mcp_integration first. Use update_mcp_server when changing only a Portkey server instance's display metadata.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>"
},
"name": "update_mcp_integration"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The MCP integration ID or slug to update | |
| url | No | New URL endpoint | |
| name | No | New display name | |
| tags | No | Key-value tags. Replaces existing tags; pass null to clear. Keys allow letters, numbers, underscores, and hyphens | |
| auth_type | No | New authentication type. Current examples are 'none', 'headers' (custom headers), and 'oauth_auto' (OAuth); Portkey may accept additional values. | |
| transport | No | New transport protocol | |
| description | No | New description | |
| configurations | No | Replacement documented or forward-compatible configuration fields. configurations.custom_headers must be a string-to-string header map when present. | |
| custom_headers | No | New custom headers for authentication. Sent via configurations.custom_headers | |
| secret_mappings | No | Replacement runtime Secret Reference mappings; each target_field must be unique |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | Call succeeded | |
| data | No | Success payload | |
| error | No | Failure details |