All integrations
K
Kubernetes
Any Kubernetes cluster API, through kubectl or direct HTTP.
Cloud and infrastructure
How an agent reaches it
- MCP
No official MCP server yet. The REST lane covers the same ground.
- REST API
Always available. The agent calls the API directly with your credential attached.
- CLI
The `kubectl` command, run on one of your computers with the credential mounted.
How you authenticate
- API key
- Create a ServiceAccount with a role bound to only what the agent needs, then mint a token for it.
- Store the kubeconfig as a FILE credential if you want the kubectl lane.
- There is no fixed host: the API server address belongs to your cluster, so set a URI rule for it explicitly.
How agents reach it
- Base URL
- https://{apiserver}
- Pagination
- cursor
- CLI
- kubectl
Common endpoints
| list namespaces | GET /api/v1/namespaces |
| list pods | GET /api/v1/namespaces/{ns}/pods |
| list deployments | GET /apis/apps/v1/namespaces/{ns}/deployments |
Worth knowing
- Clusters commonly use a private CA, so certificate verification needs the cluster CA bundle. The kubectl lane handles this.
- kubectl is almost always simpler than raw HTTP here.