Light Cloud MCP

Light Cloud MCP Server

An MCP (Model Context Protocol) server that enables Claude to deploy and manage applications on Light Cloud Platform.

No account yet? Start here

Ask Claude: "Sign me up for Light Cloud as you@example.com" (or "connect me to Light Cloud"). The connect tool creates the account — Free plan, no card, no password, no form — once you approve a short code at console.light-cloud.com/device from any device. Same tool signs an existing account in. Then: "deploy this project", "add a database", "put the workspace on Lite". Nothing needs the web console.

Features

• Sign-up and sign-in from the terminal - connect with an email; a code approved on any device creates or signs in the account. No password.
• Billing from the conversation - plans, included usage, a one-step upgrade through Stripe Checkout (monthly or annual)
• Application management - Create, deploy, and delete applications
• Environment management - Manage staging, production, and preview environments
• GitHub integration - Deploy directly from GitHub repositories
• Upload deployment - Deploy local projects without GitHub
• Logs, metrics, rollbacks - runtime and build logs, environment metrics and activity, one-call rollback
• Framework detection - the uploaded folder is read by the same detector the console uses for a repository
• Password-protected sites - password on deploy gates the site at the edge from the first request
• Console parity - settings, folders, stacks, database admin (schema, SQL, dump, import), invoices and usage alerts, workspace members, API keys (paid plans), git provider links, notifications, support
• An off switch you control - Settings → Security → Agents & CLI in the console decides what agents may do; enforced on the backend

Installation

Claude Code

# Add the MCP server

claude mcp add light-cloud -- npx @light-cloud/mcp-server

Then inside Claude Code, allow all tools without repeated prompts:

/allowed add mcp__light-cloud__*

Claude Desktop (one-click extension)

Download light-cloud- .mcpb from the latest release and open it — Claude Desktop shows an install dialog. The bundle carries the server and its dependencies; Node ships with Claude Desktop, so nothing else is needed. Settings (API endpoint, console URL) are editable in the extension's page.

Build it yourself: npm run bundle → release/light-cloud- .mcpb (manifest.json in this repository is the generated manifest).

Claude Desktop (manual config)

Add to your claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{

"mcpServers": { "light-cloud": { "command": "npx", "args": ["@light-cloud/mcp-server"] } } }

Usage

Once installed, just chat naturally with Claude:

You: Deploy my React app to Light Cloud

Claude: I'll help you deploy. First, let me check your authentication... [Opens browser for login]

You: Show me all my applications Claude: [Lists your applications with status]

You: Check the logs for my-app Claude: [Fetches and displays recent logs]

Available Tools

110 tools: everything the console can do, from a conversation. Console-only by design: the account password, two-factor settings, and the Agents & CLI switch (below). Full reference with a prompt for each tool: https://docs.light-cloud.com/deploy-with-ai/mcp-server#tool-reference

Prompt: deploy-from-scratch — asks the two things a folder cannot answer (workspace, public or password-protected), then deploys and hands back the URL.

Turning agents off

Settings → Security → Agents & CLI in the console decides what this server, the CLI and the VS Code extension may do on an account: a master switch, then groups (deploy, delete, settings, databases, billing, workspace, API keys). Reads are always allowed. The backend enforces it from the session's own client claim, fixed when the session was issued, so a header cannot get around it — and the switch can only be changed from the console. A refusal comes back as AGENT_ACCESS_DISABLED or AGENT_ACTION_BLOCKED with the place to change it; the server's instructions tell the assistant not to retry.

Authentication

Two ways in; both store credentials in ~/.lightcloud/credentials.json.

`connect` (default, works anywhere). Ask Claude to connect with your email. The tool prints an 8-character code and the address console.light-cloud.com/device; open it on any device, sign in if you already have an account (or follow the link in the email we sent if you do not — approving creates the account), type the code, approve. Claude calls connect-status until the approval lands. No password is typed into Claude, ever.

`login` (browser on this machine). Opens the console's sign-in page with a loopback callback, as before.

Plans and upgrading

Every workspace starts on Free: $1 of usage a month, unlimited static sites, 3 server apps, no card. When Free's $1 is used up, server apps and deploys pause until the next cycle and static sites keep serving; a free workspace is never billed. Paid plans (Lite, Starter, Pro, Business; list-plans has prices and limits) include usage worth their price, extra usage goes on the next invoice, and a usage limit can be chosen at checkout. Annual billing is two months free.

Upgrading is one step. choose-plan (with interval: "year" for annual billing) charges a saved card, or returns a Stripe Checkout link that takes the card and the first payment together. The assistant hands over the link ("Open this link to add a card; the plan switches as soon as Stripe confirms") and payment-method-status waits until the plan has switched. add-payment-method only saves or replaces a card. No card number passes through the server.

Refusals an agent can act on

Write tools that hit a plan limit come back with a code and a Next step: line. A plan refusal (PLAN_ENTITLEMENT) names the plan that includes what was refused and its price, for example Next step: call the choose-plan tool with plan_id lite (Lite, $5/month) once the user agrees; the assistant asks the user before upgrading, since choose-plan takes payment. Others: PAYMENT_METHOD_REQUIRED → add-payment-method, POOL_EXHAUSTED → choose-plan (Free's included usage is used up), ORGANISATION_SUSPENDED → add-payment-method. The deploy-from-scratch prompt walks the whole path: connect, billing check, detect, create, database + environment variables, deploy.

Some refusals are answered by talking to the user instead:

Custom domains come with the paid plans. On Free add-custom-domain is refused with PLAN_ENTITLEMENT, naming the plan that includes them. A domain already on a Free workspace goes on hold 14 days after the owner is emailed (the site keeps its light-cloud.io address), and a database left on Free stops then too, with its data kept; a paid plan brings both back. Downgrading to Free with a database is refused with DATABASES_ON_FREE until it is deleted. Pages on Free carry a small "by Light Cloud" link, added at the edge; list-plans says which plans show it.

Configuration

No configuration is needed. The server talks to Light Cloud at these addresses by default:

Set them only if you were given a different endpoint.

Development

# Clone the repository

git clone https://github.com/light-cloud-com/mcp-server.git cd mcp-server

Install dependencies

npm install

Run in development mode

npm run dev

Build for production

npm run build

Testing

Test the server manually:

npm run build

node dist/index.js

Then send JSON-RPC messages via stdin.

License

MIT - see LICENSE

Links

• Light Cloud Platform
• MCP Documentation
• Report Issues

Submitting to the Anthropic directory

What the Software Directory policy asks for and where it is:

• Bundle: the .mcpb on the latest release; source in this repository.
• Tool annotations (title, readOnlyHint, `des