Docs: update docs for using unified kubectl tool #90
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request updates the README documentation to introduce and explain the new unified kubectl tool mode alongside the legacy multi-tool mode. The changes help users understand the difference between the two modes and how to configure them.
- Added documentation for the
USE_LEGACY_TOOLSenvironment variable to toggle between unified and legacy tool modes - Restructured the "Available Tools" section to clearly distinguish between the default unified
call_kubectltool and optional legacy tools - Simplified the "Access Levels" section to focus on operation filtering rather than tool availability
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - **Parameters**: | ||
| - `command`: The full kubectl command to execute (e.g., "get pods -n default", "apply -f deployment.yaml") | ||
| - **Examples**: | ||
| ```bash |
There was a problem hiding this comment.
The code block uses bash syntax highlighting, but the examples show parameter values for a JSON/YAML configuration, not actual bash commands. Consider using a plain text code block or a more appropriate language identifier like yaml or text to avoid confusion.
Suggested change
| ```bash | |
| ```yaml |
mainred
approved these changes
Dec 1, 2025
Fei-Guo
approved these changes
Dec 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the documentation in the
README.mdfile to clarify the usage of unified and legacy tool modes for themcp-kubernetesserver, and to improve explanations around access levels and available tools. The changes make it easier for users to understand how to configure and use the server in both modes, and how operations are filtered by access level.Tool configuration and usage:
USE_LEGACY_TOOLSenvironment variable, which allows switching between unified and legacy tool modes.call_kubectltool (default) and the legacy mode with multiple specialized tools, including example configuration for enabling legacy mode.Access levels and filtering:
Documentation structure: