DeleteApiMcpServer-阿里云帮助中心

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

openapiexplorer:DeleteApiMcpServer

delete

*ApiMcpServer

acs:openapiexplorer::{#accountId}:apimcpserver/{#id}

None

Request syntax

DELETE /apimcpserver HTTP/1.1

Request parameters

Parameter	Type	Required	Description	Example
clientToken	string	No	A client-generated token that you must use to ensure request idempotence. The token must be unique for each request, contain only ASCII characters, and be no longer than 64 characters. Using a UUID is recommended. The token is valid for 3 days.	123e4567-e89b-12d3-a456-426655440000
id	string	Yes	The ID of the API MCP service.	v6ZZ7ftCzEILW***

Response elements

Element	Type	Description	Example
	object	The response.
requestId	string	The request ID.	9BFC4AC1-6BE4-5405-BDEC-CA288D404812

Examples

Success response

JSON format

{
  "requestId": "9BFC4AC1-6BE4-5405-BDEC-CA288D404812"
}

Error codes

HTTP status code	Error code	Error message	Description
400	Missing.Id	Id is mandatory for this action.
400	IdempotentParameterMismatch	The request uses the same client token as a previous request but with different parameters. Client tokens should not be reused across non-identical requests. Each unique request must have a distinct client token.	The request used the same client token as the previous request, but with different parameters. Do not reuse the same token in requests with different parameters. Each request must use a unique token.
400	InvalidParam.ClientToken	The specified client token is not valid.	The idempotent parameter is incorrect, please check.
403	OperationNotAllowed.SystemServer	System type servers are not allowed to be updated or deleted.	System-level services do not allow update or delete operations.
404	NotFound.ApiMcpServer	Specified MCP server not found.	The MCP service with the specified ID does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.