Kubeadapt MCP
Other MCP clients
Connect any AI tool that supports remote MCP servers to Kubeadapt: the server URL, how sign-in works, and a bridge for tools that only run local servers.
Kubeadapt MCP follows the open Model Context Protocol, so any AI tool that supports remote MCP servers can connect, including ones not listed in these docs.
Connection details
| Server URL | https://mcp.kubeadapt.io/mcp |
| Transport | Streamable HTTP |
| Sign-in | OAuth 2.1 with PKCE, discovered from the server; no API key |
| Client registration | Client ID Metadata Documents, or dynamic client registration |
| Access | Read-only |
Add the server URL in your tool's MCP settings. When the tool first connects, Kubeadapt answers that sign-in is needed and tells the tool where to send you. The tool opens Kubeadapt in your browser, where you sign in, choose the kinds of data and the clusters it may read, and select Allow Access.
Tools that sign in through a local callback, such as http://127.0.0.1:<port>/callback, can use any port.
Configure several tools at once
add-mcp adds a server to the AI tools it finds on your machine in one step:
npx add-mcp https://mcp.kubeadapt.io/mcpThen sign in from each tool as it asks.
Tools that only run local servers
If your AI tool can only start MCP servers as local commands, mcp-remote bridges it to a remote server and handles sign-in for it:
1{
2 "mcpServers": {
3 "kubeadapt": {
4 "command": "npx",
5 "args": ["-y", "mcp-remote", "https://mcp.kubeadapt.io/mcp"]
6 }
7 }
8}Verified AI tools
Kubeadapt verifies an AI tool when the web address that signs it in belongs to the tool's maker, for example claude.ai or chatgpt.com, and names it on the consent page. Any tool can connect unless an admin allows only verified ones; the access policy under Settings → Kubeadapt MCP lists the verified tools. See Permissions and security.