Helm charts and platform-mesh integration for the kcp MCP stack:
- charts/access-vw — the access virtual workspace: permission-aware workspace discovery (
SelfClusterAccessReview) served through the kcp front proxy. - charts/mcp-vw — the MCP virtual workspace: an MCP server that scopes every session to the workspaces the caller can access and acts on resources via impersonation, so kcp authorizes each request as the caller.
Both charts render kcp-operator VirtualWorkspace and Kubeconfig resources (operator v0.9.0 or newer required).
Prerequisites: a running platform-mesh local-setup kind cluster with kcp-operator >= v0.9.0, a kcp admin kubeconfig (local-setup/scripts/createKcpAdminKubeconfig.sh), mkcert, helm, jq.
KCP_ADMIN_KUBECONFIG=/path/to/helm-charts/.secret/kcp/admin.kubeconfig \
hack/setup-platform-mesh.shThe script installs both charts, adds /services/access and /services/mcp front-proxy path mappings, enables OIDC bearer-token authentication against the local-setup Keycloak, exposes the MCP server with OAuth discovery on https://mcp.portal.localhost:8443/services/mcp, binds the APIExport and impersonator RBAC in the demo workspaces, seeds a demo user ([email protected]), and verifies the stack end to end.
Connect an MCP client: point it at https://mcp.portal.localhost:8443/services/mcp with no credentials. The client discovers Keycloak via OAuth protected-resource metadata (RFC 9728), registers itself, and opens a browser login — sign in as the demo user ([email protected] / alice-password). The TLS certificate is the mkcert root, already trusted on the machine that ran local-setup.
For GitHub Copilot Chat, copy examples/copilot/mcp.json to .vscode/mcp.json and start the kcp MCP server. The tools then operate exclusively on the workspaces the logged-in user can access.
For scripting or debugging without a browser, hack/get-token.sh prints a bearer token for the demo user that can be passed as an Authorization header directly.
This repository is an incubation space. The target shape upstreams the stack into platform-mesh itself:
- contrib-virtual-workspaces:
expose the access and MCP virtual workspaces as embeddable library
constructors (today the serve logic is
internal/), so consumers can mount them into an existingvirtual-workspace-frameworkroot API server. - platform-mesh/platform-mesh:
services/virtual-workspaces(built on the same framework) imports the contrib module and mounts both virtual workspaces alongside its own, with flags for the SCAR endpoint and OIDC/OAuth configuration. They then ship in the existingvirtual-workspacesimage — no separate images, charts, or OCM component. - platform-mesh/helm-charts:
the existing
virtual-workspaceschart gains the new flags as values plus an HTTPRoute for the MCP hostname (OAuth discovery metadata must be served anonymously, which the front-proxy does not allow). Keycloak needs no changes: users authenticate with their existing platform-mesh accounts, and the AI gateway is registered as a single OAuth client through the existing realm configuration. The anonymous dynamic client registration relaxation used by the demo here does not migrate.
Once that lands, this repository reduces to client examples and demo scripts
for standalone (non-platform-mesh) kcp installations, which keep using the
charts published from charts/.
This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.
If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.
Please refer to our Code of Conduct for information on the expected conduct for contributing to Platform Mesh.
