All Products
Search
Document Center

API Gateway:UpdateMcpServer

Last Updated:Dec 17, 2025

Updates an MCP server.

Operation description

You can only update the listening Ingress configuration for sources of the ACK type.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • For mandatory resource types, indicate with a prefix of * .
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
apig:UpdateMcpServernone
*All Resources
*
    none
none

Request syntax

PUT /v1/mcp-servers/{mcpServerId} HTTP/1.1

Request parameters

ParameterTypeRequiredDescriptionExample
bodyobjectNo

The request body.

descriptionstringNo

The description.

domainIdsarrayNo

The domain IDs.

stringNo

The domain ID.

d-cr62ts5lhtgln***
matchHttpRouteMatchNo

The route match rule.

backendConfigobjectNo

The backend service configurations for the route.

scenestringNo

The backend service scenario.

SingleService
servicesarray<object>No

The backend services.

objectNo

The backend service.

protocolstringNo

The service protocol. Valid values:

  • TCP
  • HTTP
  • DUBBO
HTTP
portintegerNo

The service port (omit for dynamic ports).

8080
weightintegerNo

The traffic weight percentage.

49
serviceIdstringNo

The service ID.

svc-cr6pk4tlhtgm58e***
versionstringNo

The service version.

v1
exposedUriPathstringNo

The exposed URI path. This parameter is required when the protocol parameter is set to SSE or StreamableHTTP and the type parameter is set to RealMCP.

/sse
assembledSourcesarray<object>No

The list of assembly sources. This parameter is required when the type parameter is set to AssemblyMCP.

objectNo

The assembly source. This parameter is required when the type parameter is set to AssemblyMCP.

mcpServerNamestringNo

The name of the MCP server.

test-mcp
mcpServerIdstringNo

The MCP server ID.

mcp-afaefaefaf
toolsarrayNo

The MCP tools.

stringNo

The MCP tool.

tool-1
mcpStatisticsEnablebooleanNo

Specifies if MCP observability is enabled. Default value: false.

false
typestringYes

The MCP server type. Valid values: RealMCP and AssemblyMCP.

RealMCP
protocolstringYes

The service protocol. Valid values: HTTP, HTTPS, SSE, and StreamableHTTP.

HTTP
createFromTypestringNo

Specifies the type of source for MCP server creation.

mcpServerIdstringNo

The MCP server ID.

mcp-adfefz24afg

Response parameters

ParameterTypeDescriptionExample
object

Schema of Response

requestIdstring

The request ID.

3ACFC7A7-45A9-58CF-B2D5-765B60254695
codestring

The status code.

Ok
messagestring

The status message.

success

Examples

Sample success responses

JSONformat

{
  "requestId": "3ACFC7A7-45A9-58CF-B2D5-765B60254695",
  "code": "Ok",
  "message": "success"
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2025-12-05The internal configuration of the API is changed, but the call is not affectedView Change Details
2025-11-06The internal configuration of the API is changed, but the call is not affectedView Change Details