Cloudfleet AI Agents

The Cloudfleet plugin gives AI coding agents the knowledge and tools to work with Cloudfleet Kubernetes Engine (CFKE) and Cloudfleet Container Registry (CFCR). It bundles three parts:

• Skills: guided workflows for cluster and Fleet setup with the CLI or Terraform, self-managed nodes, cluster debugging, and container images, plus background knowledge on CFKE architecture and production best practices. The agent loads a skill when your request needs it.
• MCP server: the Cloudfleet MCP server, preconfigured, so the agent can inspect clusters, Fleets and Kubernetes resources and manage support tickets.
• Feedback prompts: hooks that ask the agent to assess Cloudfleet work when a Cloudfleet command or tool fails, and occasionally after it succeeds. The agent drafts feedback for the Cloudfleet team and sends it only after you approve the draft.

The plugin is open source in the cloudfleetai/agents repository. One repository serves every supported agent, and each agent installs it through its own plugin system.

Supported agents

For an agent that is not on this list, connect the MCP server directly. You get the MCP tools without the skills and feedback prompts.

Prerequisites

• The Cloudfleet CLI 1.11.0 or later, the first release with cloudfleet agents. Check your version with cloudfleet --version.
• An authenticated CLI profile. The MCP server uses this profile’s permissions.
• At least one supported agent, with its command on your PATH: claude, codex, copilot, agy, cursor-agent or kiro-cli.
• jq, which the feedback hooks need. Without jq, the hooks stay silent and the rest of the plugin works.
• Optional: kubectl. The skills use it when it is installed and fall back to the MCP server when it is not.

Install with the CLI

Run cloudfleet agents setup:

cloudfleet agents setup

The command finds every supported agent on your PATH, shows what each one has installed, and asks before it changes anything. For each agent, it runs the agent’s own plugin installer and then checks that the agent loads the plugin. Where an agent supports it, the command also turns on automatic plugin updates.

When the command finishes, it prints what is left to do in each agent:

• Claude Code: restart Claude Code, or run /reload-plugins in a running session.
• Codex: on the next launch, Codex asks you to trust the Cloudfleet hooks. Review them under /hooks. Codex asks again after every plugin update, because its trust covers the content of the installed plugin.
• Cursor: Cursor has no command that installs a plugin, so the setup only adds the Cloudfleet marketplace. Run /plugins in cursor-agent, or open Customize in the Cursor app, and install cloudfleet.
• Kiro CLI: only the V3 engine (kiro-cli --v3) loads the plugin. The setup also adds the Cloudfleet MCP server to Kiro’s global configuration, so the default engine gets the MCP tools too.

The CLI also offers the setup after a browser login, when an agent on your machine lacks the plugin. If you decline, it prints the setup command for later.

Options

When you run the command inside a coding agent, it sets up only that agent, because it is the one you are working in. Pass --client to set up a different one.

Check what is installed

cloudfleet agents status lists each supported agent with the installed plugin version and whether automatic updates are on:

cloudfleet agents status

The command changes nothing. Add --json for machine-readable output.

Keep the plugin up to date

To update the plugin in every agent, run cloudfleet agents setup again. It updates agents that have the plugin and installs it in agents that do not.

Most agents update the plugin on their own:

• Claude Code and GitHub Copilot CLI: cloudfleet agents setup turns on automatic updates for the Cloudfleet marketplace in ~/.claude/settings.json and ~/.copilot/settings.json. Claude Code installs an update in the background and loads it on the next launch or after /reload-plugins.
• Codex: updates plugins from Git marketplaces on its own.
• Antigravity CLI and Kiro CLI: cannot update plugins on their own. Run cloudfleet agents setup to update.
• Cursor: cannot update plugins from a GitHub marketplace on its own. Reinstall cloudfleet from /plugins in cursor-agent, or from Customize in the Cursor app.

Environment variables that turn off an agent’s updates also turn off its plugin updates: DISABLE_AUTOUPDATER, DISABLE_UPDATES or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC for Claude Code, and COPILOT_AUTO_UPDATE=false for Copilot CLI. cloudfleet agents status then reports automatic updates as off. To keep Claude Code plugin updates on while its own updates are off, set FORCE_AUTOUPDATE_PLUGINS=1.

For every install that does not update on its own, the CLI checks once a day whether a newer plugin version exists. If one does, the next cloudfleet command you run in a terminal prints a notice with the update command.

To install the plugin by hand, or to see which commands the setup runs, see Install manually.

Install manually

cloudfleet agents setup installs the plugin with each agent’s own plugin commands. To install it by hand, for example on a machine without the Cloudfleet CLI 1.11.0, run the same commands yourself. The marketplace is named cloudfleet in every agent.

The plugin’s MCP server and skills call the cloudfleet command, so the CLI must still be installed and authenticated.

claude plugin marketplace add cloudfleetai/agents
claude plugin install cloudfleet@cloudfleet

/plugin marketplace add cloudfleetai/agents
/plugin install cloudfleet@cloudfleet
/reload-plugins

codex plugin marketplace add cloudfleetai/agents
codex plugin add cloudfleet@cloudfleet

copilot plugin marketplace add cloudfleetai/agents
copilot plugin install cloudfleet@cloudfleet

agy plugin install https://github.com/cloudfleetai/agents

cursor-agent plugin marketplace add https://github.com/cloudfleetai/agents

Turn on automatic updates

Claude Code and GitHub Copilot CLI update plugins from a third-party marketplace only when you turn it on. cloudfleet agents setup turns it on for you.

In Claude Code, run /plugin, open Marketplaces, select cloudfleet, and choose Enable auto-update.

For Claude Code and Copilot CLI, you can also add the marketplace entry to ~/.claude/settings.json or ~/.copilot/settings.json. A settings entry takes precedence over the toggle in /plugin:

{
  "extraKnownMarketplaces": {
    "cloudfleet": {
      "source": { "source": "github", "repo": "cloudfleetai/agents" },
      "autoUpdate": true
    }
  }
}

Codex updates plugins from Git marketplaces on its own.

Update by hand

Remove the plugin

If ~/.claude/settings.json or ~/.copilot/settings.json has an extraKnownMarketplaces.cloudfleet entry, remove it too. cloudfleet agents setup writes this entry to turn on automatic updates.

Try it

After you install the plugin, try prompts like these:

• “I’m getting started with Cloudfleet”
• “What clusters do I have?”
• “Create a new cluster with a Hetzner Fleet”
• “Write Terraform for a CFKE cluster with a Hetzner Fleet”
• “Check if my cluster follows best practices”
• “Debug my cluster, Pods are stuck in Pending”
• “Push my app image to CFCR”
• “Add a self-managed node to my cluster”

Contact Cloudfleet from your agent

The plugin’s contact skill picks the right channel for what you need:

• Support tickets for problems that need an answer or an investigation, and for billing questions. The agent opens and follows up on tickets with the tickets_* MCP tools or cloudfleet tickets. See Support tickets.
• Roadmap for concrete feature requests. The agent lists existing items, votes on them, or suggests a new one with cloudfleet roadmap.
• Feedback for quick one-way notes, such as wrong docs, confusing errors or what worked well. The agent sends it with the feedback_send MCP tool or cloudfleet feedback. The team reads every message but does not reply.

For every channel, the agent shows you the draft and sends it only after you approve.

Security considerations

The plugin runs cloudfleet mcp with your CLI profile and inherits its permissions. Cluster and Kubernetes data are read-only through the MCP server, but the skills can propose CLI and Terraform commands that change infrastructure. Review commands before your agent runs them, especially commands that create, update or delete clusters and Fleets. For details on what the MCP server can access, see Security considerations.