Skip to content

About

CloudPilot product knowledge and read-only MCP plugins for coding agents.

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

7 Commits

Folders and files

Repository files navigation

CloudPilot Agent Plugins

Preview plugins for explaining CloudPilot product fields and behavior with official documentation and relevant read-only MCP data. Codex and Claude Code share one lightweight skill; each client has its own plugin manifest.

The current milestone covers documentation retrieval, field explanations, and read-only observations. Validated configuration-recommendation strategies are planned for a later milestone. This package does not apply settings or perform cluster operations.

Prerequisites

  • A client version that supports plugin marketplaces and remote HTTP MCP.
  • Your own CloudPilot account and permission to access the selected organization.
  • A CloudPilot MCP deployment exposing the search and fetch knowledge tools. Backend releases are independent of this plugin. Installing the plugin or completing OAuth does not prove those tools are available.

The bundled production endpoint is https://mcp.cloudpilot.ai/mcp. Sign in through your client's OAuth flow and verify the account and organizations before granting access. Do not copy tokens into the plugin or repository.

Install

The repository commands below use the default branch after the package is merged. For an unmerged preview or local backend, use the checkout workflow in the package guide.

Codex

Register the repository marketplace:

codex plugin marketplace add cloudpilot-ai/agent-plugins

Restart the desktop app, open Plugins, choose CloudPilot Plugins (Preview), and install CloudPilot. Complete the connection's authorization flow when requested. See the official packaging documentation for client-specific marketplace support.

Start a fresh conversation and explicitly select the installed CloudPilot knowledge skill for an initial test. Natural questions can also select the skill, but selection depends on the client and prompt; it is not guaranteed.

Claude Code

Run these commands in a shell:

claude plugin marketplace add cloudpilot-ai/agent-plugins
claude plugin install cloudpilot@cloudpilot-agent-plugins

Start a new session, use /mcp to inspect and authorize the CloudPilot connection, then invoke /cloudpilot:cloudpilot-knowledge. See the official marketplace documentation.

Avoid loading a standalone copy of the same skill or enabling a duplicate MCP connection during testing. Preserve existing credentials and unrelated services; do not clear global authentication to troubleshoot this plugin.

Update

You can ask your agent: "Check for a CloudPilot plugin update" or "Update my CloudPilot plugin, keeping my existing MCP connection and login." The skill can optionally check once per conversation and mention a confirmed newer stable version after answering. Upgrade instructions load only when you ask to update; normal questions do not load them. This is best-effort guidance, not a background updater or a guaranteed client notification. Older installations need one native update before they gain this workflow. See the changelog for package changes.

Codex

Refresh the CloudPilot marketplace and inspect the installed version:

codex plugin marketplace upgrade cloudpilot-agent-plugins
codex plugin list --marketplace cloudpilot-agent-plugins --json

Verify the installed version rather than just the available catalog version. Restart the desktop app and start a new conversation to load updated files. If the installed version remains old, report the incomplete update and inspect the native plugin UI for supported update actions; do not uninstall/reinstall. Use the CLI bundled with the desktop app when managing that installation. See the official commands.

Claude Code

Run from a shell, preserving the installed scope (--scope when necessary):

claude plugin marketplace update cloudpilot-agent-plugins
claude plugin update cloudpilot@cloudpilot-agent-plugins

Verify the installed version, then use /reload-plugins if supported or start a new session. For native automatic updates, open /plugin, select Marketplaces, choose CloudPilot, and enable auto-update. Third-party marketplaces default to auto-update off; publishers cannot enable it for users. See the official update guidance.

Neither update flow requires removing the plugin or clearing OAuth credentials. Public product documentation comes from remote MCP and does not require a local plugin update for every documentation change. Fixed-ref and local/test installs are not automatically moved to the stable channel.

Try it

  • What does minNonSpotReplicas mean in CloudPilot?
  • How do CPU used, requested, allocatable, and provisioned differ?
  • Does enabling Image Accelerator prove images are pulled from peers?
  • For my selected cluster, explain its NodePool consolidation settings.

Documentation-only questions should not read cluster inventory. Cluster-specific questions need a selected connection and relevant read permissions. If knowledge tools or required evidence are missing, the expected response is an explicit limitation, not an invented answer or a switch to another environment.

Connecting MCP alone does not install this skill. The plugin bundles the skill and connection configuration, while authorization remains an interactive user step. This repository marketplace is not a listing in a client's public directory.

Maintenance

Keep procedural guidance in the shared skill, and product facts in the official documentation served by MCP. Update plugin manifests together when releasing a package change, and record changes in the changelog. Use the package guide for packaging and local testing and the evaluation cases for behavioral checks. Do not commit credentials, customer data, or transcripts.

About

CloudPilot product knowledge and read-only MCP plugins for coding agents.

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors