Tool: apply_k8s_manifest
Applies a Kubernetes manifest to a cluster using server-side apply. This is similar to running kubectl apply --server-side
.
The following sample demonstrate how to use curl
to invoke the apply_k8s_manifest
MCP tool.
| Curl Request |
|---|
curl --location 'https://container.googleapis.com/mcp' \ --header 'content-type: application/json' \ --header 'accept: application/json, text/event-stream' \ --data '{ "method": "tools/call", "params": { "name": "apply_k8s_manifest", "arguments": { // provide these details according to the tool' s MCP specification } } , "jsonrpc" : "2.0" , "id" : 1 } ' |
Input Schema
KubeApplyRequest is the request message for applying Kubernetes manifests.
ApplyK8SManifestRequest
| JSON representation |
|---|
{ "parent" : string , "yamlManifest" : string , "forceConflicts" : boolean , "dryRun" : boolean } |
| Fields | |
|---|---|
parent
|
Required. The cluster to apply the manifest to. Format: projects/{project}/locations/{location}/clusters/{cluster} |
yamlManifest
|
Required. The YAML manifest to apply. |
forceConflicts
|
Optional. If true, force conflicts resolution when applying. |
dryRun
|
Optional. If true, run in dry-run mode. |
Output Schema
KubeApplyResponse is the response message for applying Kubernetes manifests.
ApplyK8SManifestResponse
| JSON representation |
|---|
{
"result"
:
string
,
"errors"
:
[
{
object (
|
| Fields | |
|---|---|
result
|
Result of the apply operation, e.g., resources created/configured. This might be a summary string or structured data. |
errors[]
|
Errors encountered during apply. If this field is populated, some resources may not have been applied. |
Status
| JSON representation |
|---|
{ "code" : integer , "message" : string , "details" : [ { "@type" : string , field1 : ... , ... } ] } |
| Fields | |
|---|---|
code
|
The status code, which should be an enum value of |
message
|
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the |
details[]
|
A list of messages that carry the error details. There is a common set of message types for APIs to use. An object containing fields of an arbitrary type. An additional field |
Any
| JSON representation |
|---|
{ "typeUrl" : string , "value" : string } |
| Fields | |
|---|---|
typeUrl
|
Identifies the type of the serialized Protobuf message with a URI reference consisting of a prefix ending in a slash and the fully-qualified type name. Example: type.googleapis.com/google.protobuf.StringValue This string must contain at least one The prefix is arbitrary and Protobuf implementations are expected to simply strip off everything up to and including the last All type URL strings must be legal URI references with the additional restriction (for the text format) that the content of the reference must consist only of alphanumeric characters, percent-encoded escapes, and characters in the following set (not including the outer backticks): In the original design of |
value
|
Holds a Protobuf serialization of the type described by type_url. A base64-encoded string. |
Tool Annotations
Destructive Hint: ✅ | Idempotent Hint: ✅ | Read Only Hint: ❌ | Open World Hint: ❌

