LIGHTCLOUD

Deploy with AI

Deploy by asking your AI

Ship from Claude or GitHub Copilot. Create apps, deploy them, and read logs without leaving your chat or your editor.

Claude · MCP serverIdle
Deploy this repo
  1. detect-local-frameworkNext.js
  2. create-applicationshop
  3. deploy-applicationproduction
https://shop.light-cloud.io
Copilot Chat · VS Code

❯ @lightcloud /deploy

React (Vite) · building…

Live · https://shop.light-cloud.io

❯ @lightcloud /status

Deployedshop · production

Same deploy, asked two ways — both come back with a live URL.

Two surfaces

Your chat or your editor.

Pick the one you already have open. Both talk to the same Light Cloud account and the same apps.

Claude

MCP server

Add the Light Cloud MCP server to Claude, sign in once through your browser, and ask Claude to deploy. It can create apps, ship them, manage environments, and read logs.

  • Browser sign-in, credentials stored locally
  • Create apps and deploy from a conversation
  • List repositories and branches
  • Read environment logs

GitHub Copilot

VS Code extension

Install the Light Cloud extension and use @lightcloud in Copilot Chat. Slash commands cover the whole loop, and a project config file means follow-up commands need no arguments.

  • @lightcloud in Copilot Chat
  • /deploy, /redeploy, /status, /list
  • /plan to preview config before shipping
  • /destroy to tear an app down
TWO CLIENTS · ONE PLATFORMClaudeask it to deployGitHub Copilot@lightcloud /deployMCP serversign in onceVS Code extensionproject config fileLight Cloudapps · envs · logsCloud RunGlobal CDN

How it connects

Two clients, one platform.

Claude reaches Light Cloud through the MCP server. Copilot reaches it through the VS Code extension. Both end up on the same apps, environments, and logs — and deploy to Cloud Run or the global CDN like any push from GitHub.

  • Sign in once through your browser. Credentials are stored locally, not in the chat.
  • Claude calls the MCP tools directly: create-application, deploy-application, get-environment-logs, and more.
  • The VS Code extension writes a project config file, so /status and /redeploy need no arguments.
  • Everything lands in the same console, next to apps deployed from GitHub.

Automatic

Handled for you.

The parts you would otherwise type into a form are read from the repo and the working directory.

Framework detection

Your stack is detected from the repo, so you do not describe the build by hand.

.env parsing

Environment variables are read from your .env file and set on the app for you.

Instant URLs

Deploys come back with a live URL and a link to the console.

Project config

A small config file records the app, so later commands run without repeating yourself.

Set it up

Add the MCP server to Claude or install the VS Code extension, sign in once, and deploy. The docs walk through both.

Read the setup docsOpen the console