Repository navigation
cleanup: Remove legacy KMCP integration - #3223
Merged
Merged
Conversation
Kagent now uses RemoteMCPServer as its only MCP Kubernetes API. Remove the legacy deployment, controller, packaging, and UI paths so clean installs no longer carry the obsolete KMCP integration. Signed-off-by: timflannagan <[email protected]>
The MCP project scaffolder came from the legacy KMCP CLI and no longer has a deployment path after removing that integration. Remove the isolated init, build, run, add-tool, and secrets commands along with their language templates and project manifest model. Signed-off-by: timflannagan <[email protected]>
github-actions
Bot
added
the
enhancement-proposal
timflannagan
added
ignore-for-release
and removed
enhancement-proposal
github-actions
Bot
added
the
enhancement-proposal
EItanya
reviewed
Oct 15, 2026
EItanya
left a comment
EItanya
left a comment
Contributor
There was a problem hiding this comment.
I definitely think we should remove it from the base helm chart and CLI , but can we hold off removing the intergration altogether for a follow-up?
Contributor
Author
Are you advocating for splitting up this PR into multiple or holding off on removing the integration for now? I think it's pretty cheap to bring back the integration via agents these days, maintaining code that's not being used also trips up agents, etc. At least that's my 2c. |
EItanya
approved these changes
Oct 15, 2026
hsteude
pushed a commit
to prokube/kagent
that referenced
this pull request
Nov 6, 2026
# Description Removing the KMCP integration and the `kagent mcp` scaffolder in kagent-dev#3223 left the shared CLI helpers it used without callers. This removes the Docker executor, project generator, filesystem, Kubernetes config, and input prompt helpers, trims the kubectl executor to what `kagent bug-report` still uses, and drops the `logging.FromLogr` adapter whose only caller was the MCPServer catalog check. No behavior change. The remaining `deadcode` findings are public STS helpers and the `WithGRPCTransportCredentials` client option, which are intentionally kept as consumer-facing extension points. Signed-off-by: timflannagan <[email protected]>
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
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.
Description
KMCP is no longer part of kagent's runtime architecture.
RemoteMCPServeristhe supported Kubernetes resource, while Substrate owns runtime provisioning.
Remove the KMCP chart dependency, controller and service wiring, UI support for
MCPServer, and the KMCP-derivedkagent mcpproject scaffolder. Keep theRemoteMCPServerflows intact and mark the historical KMCP design assuperseded.
The scaffolder can return in a v1-aligned form if user demand warrants it.
Today it is unmaintained KMCP-era cruft with no supported v1 deployment path,
so keeping it would imply a product surface that kagent does not actually
support.
Additional Notes
This targets clean installs. Existing upgraded clusters may retain KMCP CRDs or
resources that the kagent chart no longer manages.