Deploy without opening a dashboard - install Light Cloud AI (the LCAI MCP server) in Claude Code or GitHub Copilot, script it with the Light Cloud CLI, or use the @lightcloud extension in VS Code. Sign up, pick a plan and add a card from the terminal too.

Deploy with AI

You can go from no account to a running app on a paid plan without opening a dashboard. Install Light Cloud AI, the LCAI MCP server (npm: @light-cloud/mcp-server) in Claude Code or GitHub Copilot and ask; script the same platform with the Light Cloud CLI (npm: @light-cloud/cli); or use the @lightcloud extension in VS Code.

Three ways in#

Light Cloud AI (MCP server)LCAI is the MCP server. Install @light-cloud/mcp-server in Claude Code, Claude Desktop, or GitHub Copilot in VS Code, sign in - or sign up - with a code, and ask it to create apps, deploy, read logs, pick a plan.Light Cloud CLIlc login, lc deploy, lc logs -f, lc billing. Every command takes --json, so it suits agents and CI as much as people.GitHub Copilot (VS Code)Use @lightcloud in Copilot Chat with slash commands like /deploy and /status.

Nothing left for the dashboard#

Two things used to need the console: creating an account and adding a card. Neither does now.

Sign up from the terminal. connect (MCP) or lc login --device sends you an email and shows a code. Approve on any device - a phone will do - and the account, workspace and free plan exist. No password is ever typed into a chat or a terminal.
Pay from the terminal. add-payment-method (MCP) or lc billing card add prints a Stripe-hosted link. Open it anywhere, save the card, and the tool picks it up; choose-plan / lc billing plan use does the rest. Card numbers never pass through the tools.
Refusals say what to do next. When a plan does not include a size, the free pool is used up, or a card is missing, the error names the tool or command that unblocks it, so an agent keeps going instead of stopping.

All three talk to the same platform as the console - an app created from Claude shows up on the dashboard like any other, with the same environments, logs, and settings.

What is handled for you#

Framework detection from the repository or the local folder.
Environment variables read from your .env file.
A live URL and a link to the console on every deploy.
A small project config file so follow-up commands need no arguments.

What it looks like#

Deploy this project to Light Cloud.

Create a staging environment for storefront and deploy the develop branch to it.

Why did the last deployment fail? Check the logs.

The assistant picks the right tools, chains them - look up the deployment, fetch the logs, summarize - and answers with links you can click.

Good to know#

No repository required. Both paths can deploy a local folder as an upload.
Same permissions as you. The tools act as your signed-in user; sign out any time from the conversation, or from Settings > Security > Connected devices in the console.
Everything stays inspectable. Deploys from AI land in the same deploy history with the same logs as any push.