Install
The CLI, the MCP server, and shell completion. The command is always grid.
npm install -g @cloudgrid-io/cliThe npm package is @cloudgrid-io/cli. It installs the grid command. Requires
Node.js 18 or later.
Update to the latest version:
npm update -g @cloudgrid-io/cliHomebrew
Section titled “Homebrew”brew install cloudgrid-io/tap/gridThis taps cloudgrid-io/homebrew-tap and installs the same CLI, exposing the
grid command.
Verify
Section titled “Verify”grid --versiongrid doctorgrid doctor runs diagnostic checks: Node.js version, Docker availability, config
file, API reachability, authentication status, and common port conflicts. Add
--fix to repair ~/.cloudgrid/config.yaml.
Sign in
Section titled “Sign in”grid loginOpens a browser for Google OAuth and stores a token at ~/.cloudgrid/credentials.
For headless environments use grid login --no-browser. See
Authentication for all options.
Shell completion
Section titled “Shell completion”# bashgrid completion bash >> ~/.bashrc
# zshgrid completion zsh >> ~/.zshrc
# fishgrid completion fish > ~/.config/fish/completions/grid.fishMCP server
Section titled “MCP server”The MCP server is published separately as @cloudgrid-io/mcp. It exposes the grid
actions as grid_* MCP tools so AI assistants can build and deploy for you.
Run the local (stdio) edition with no install:
npx -y @cloudgrid-io/mcpIt reuses the same ~/.cloudgrid/credentials as the CLI, so no separate login is
needed. Remote-capable clients can point at the hosted endpoint instead of running
anything locally. See the MCP reference for editions,
connect URLs, and per-client setup.
Claude Desktop one-click
Section titled “Claude Desktop one-click”Claude Desktop users can install the MCP as a Desktop Extension with no terminal
and no JSON editing — download the .mcpb bundle from the
MCP releases and open it
(Settings, Extensions, Install from file). Sign in from chat with the grid_login
tool on first use.