You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-9Lines changed: 15 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,7 @@ If you're using the native binaries you don't need to have Node or Python instal
43
43
44
44
-**✅ Lightweight**: The server is distributed as a single native binary for Linux, macOS, and Windows.
45
45
-**✅ High-Performance / Low-Latency**: Directly interacts with the Kubernetes API server without the overhead of calling and waiting for external commands.
46
+
-**✅ Multi-Cluster**: Can interact with multiple Kubernetes clusters simultaneously (as defined in your kubeconfig files).
46
47
-**✅ Cross-Platform**: Available as a native binary for Linux, macOS, and Windows, as well as an npm package, a Python package, and container/Docker image.
47
48
-**✅ Configurable**: Supports [command-line arguments](#configuration) to configure the server behavior.
48
49
-**✅ Well tested**: The server has an extensive test suite to ensure its reliability and correctness across different Kubernetes environments.
|`--port`| Starts the MCP server in Streamable HTTP mode (path /mcp) and Server-Sent Event (SSE) (path /sse) mode and listens on the specified port . |
181
-
|`--log-level`| Sets the logging level (values [from 0-9](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md)). Similar to [kubectl logging levels](https://kubernetes.io/docs/reference/kubectl/quick-reference/#kubectl-output-verbosity-and-debugging). |
182
-
|`--kubeconfig`| Path to the Kubernetes configuration file. If not provided, it will try to resolve the configuration (in-cluster, default location, etc.). |
183
-
|`--list-output`| Output format for resource list operations (one of: yaml, table) (default "table") |
184
-
|`--read-only`| If set, the MCP server will run in read-only mode, meaning it will not allow any write operations (create, update, delete) on the Kubernetes cluster. This is useful for debugging or inspecting the cluster without making changes. |
185
-
|`--disable-destructive`| If set, the MCP server will disable all destructive operations (delete, update, etc.) on the Kubernetes cluster. This is useful for debugging or inspecting the cluster without accidentally making changes. This option has no effect when `--read-only` is used. |
186
-
|`--toolsets`| Comma-separated list of toolsets to enable. Check the [🛠️ Tools and Functionalities](#tools-and-functionalities) section for more information. |
|`--port`| Starts the MCP server in Streamable HTTP mode (path /mcp) and Server-Sent Event (SSE) (path /sse) mode and listens on the specified port . |
182
+
|`--log-level`| Sets the logging level (values [from 0-9](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md)). Similar to [kubectl logging levels](https://kubernetes.io/docs/reference/kubectl/quick-reference/#kubectl-output-verbosity-and-debugging). |
183
+
|`--kubeconfig`| Path to the Kubernetes configuration file. If not provided, it will try to resolve the configuration (in-cluster, default location, etc.). |
184
+
|`--list-output`| Output format for resource list operations (one of: yaml, table) (default "table") |
185
+
|`--read-only`| If set, the MCP server will run in read-only mode, meaning it will not allow any write operations (create, update, delete) on the Kubernetes cluster. This is useful for debugging or inspecting the cluster without making changes. |
186
+
|`--disable-destructive`| If set, the MCP server will disable all destructive operations (delete, update, etc.) on the Kubernetes cluster. This is useful for debugging or inspecting the cluster without accidentally making changes. This option has no effect when `--read-only` is used. |
187
+
|`--toolsets`| Comma-separated list of toolsets to enable. Check the [🛠️ Tools and Functionalities](#tools-and-functionalities) section for more information. |
188
+
|`--disable-multi-cluster`| If set, the MCP server will disable multi-cluster support and will only use the current context from the kubeconfig file. This is useful if you want to restrict the MCP server to a single cluster. |
187
189
188
190
## 🛠️ Tools and Functionalities <aid="tools-and-functionalities"></a>
189
191
@@ -207,12 +209,16 @@ The following sets of tools are available (all on by default):
207
209
208
210
### Tools
209
211
212
+
In case multi-cluster support is enabled (default) and you have access to multiple clusters, all applicable tools will include an additional `context` argument to specify the Kubernetes context (cluster) to use for that operation.
213
+
210
214
<!-- AVAILABLE-TOOLSETS-TOOLS-START -->
211
215
212
216
<details>
213
217
214
218
<summary>config</summary>
215
219
220
+
-**configuration_contexts_list** - List all available context names and associated server urls from the kubeconfig file
221
+
216
222
-**configuration_view** - Get the current Kubernetes configuration content as a kubeconfig YAML
217
223
-`minified` (`boolean`) - Return a minified version of the configuration. If set to true, keeps only the current-context and the relevant pieces of the configuration for that context. If set to false, all contexts, clusters, auth-infos, and users are returned in the configuration. (Optional, default true)
![openshift-merge-bot[bot]](https://avatars.githubusercontent.com/in/412865?v=4&size=40){kind=avatar}
0 commit comments