Connect Claude Code or Cursor to Ownkube over MCP
Release 09 Jul 16 to 22
Ask your coding agent to deploy. Ownkube now runs a hosted MCP server, so Claude Code, Cursor or any MCP client can work in your organization after one browser sign-in. okctl grew up the same week: it can create and change deployments and environments, and create and destroy clusters.
One URL, and your coding agent is in
Point any MCP client, such as Claude Code or Cursor, at https://app.ownkube.io/api/mcp and sign in with OAuth in your browser. Your coding agent can then read and manage clusters, deployments and environments.
There is no token or API key to copy. The connection is authorized with OAuth in your browser and pinned to the organization you pick when you approve it. The agent sees what your account can see, with the same role limits.
Add the server to Claude Code with the command below, then run /mcp, choose ownkube and sign in.
$ claude mcp add --transport http ownkube https://app.ownkube.io/api/mcp MCP server docs okctl can now make changes too
okctl deploy creates, updates, copies, promotes, rolls back and deletes deployments, and resets a database password. A script or a coding agent can now do more than look.
okctl deploy create -f app.json creates a deployment from a manifest in JSON or YAML, and -f - reads it from stdin. okctl deploy update <id> -f app.json applies a changed manifest as a new revision.
$ okctl deploy rollback <deployment-id> <revision-id> Command reference A cluster in your AWS account from one command
okctl clusters create starts a Starter or Production (EKS) cluster in your own AWS account. status, cancel and delete follow it, stop it or tear it down.
Use --type starter for one instance with no Ownkube fee, or --type production for a managed EKS cluster. okctl clusters status <cluster-id> shows it coming up.
$ okctl clusters create --name dev --account <aws-account-id> --region eu-central-1 --type starter Create a cluster More in this release
- Environments from the terminal. `okctl environments create`, `update`, `set-env` and `delete` manage environments and their shared variables.
- MCP sign-in stays in one window. Signing in with a social provider while connecting an agent no longer opens a second popup and strands the approval in the wrong window.
- Closing the quick start still creates your cluster. Closing the quick start after you configure a cluster creates it in the background. The dialog also notes that clusters can launch in any region and that running the AWS stack is free.
- The top bar fits a narrow window. Long cluster names, image references, repository names and member rows truncate instead of overflowing, and the command bar no longer collides with the cluster selector.