Light Cloud MCP

Name: Light Cloud MCP
Author: light-cloud-com

by light-cloud-comversion 1.6.2i★ –iRuns on your computer

Registry namecom.light-cloud/mcp-server

Install

Overview

Description from the maker (original English)

Deploy and run web apps, APIs and databases on Light Cloud from your AI agent.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "light-cloud": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@light-cloud/mcp-server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain light-cloud.com (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 1389 servers in this category
Published to the registry more recently than 82% of the other 1389 servers in this category
Basic checks equal to or better than 100% of the other 1389 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Light Cloud MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.6.2) reached the registry 9 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 15 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Group	Tools
Account	`connect`, `connect-status`, `login`, `logout`, `whoami`, `get-profile`, `update-profile`, `list-connected-devices`, `sign-out-device`, `get-agent-access`
Deploy	`upload-and-deploy` (with optional `password`), `create-application`, `create-stack`, `wait-for-deployment`, `deploy-application`, `deploy-environment`, `rollback-deployment`, `set-password-protection`, `detect-local-framework`, `detect-framework`, `detect-local-git`, `list-repo-directories`, `read-project-config`, `write-project-config`
Apps & environments	`list-applications`, `get-application`, `get-application-status`, `get-formatted-list`, `get-formatted-status`, `update-application`, `rename-application`, `move-application`, `delete-application`, `list-environments`, `get-environment`, `create-environment`, `update-environment`, `delete-environment`, `set-scaling`, `get-environment-metrics`, `get-environment-activity`, `get-environment-runtime`, `list-folders`, `create-folder`, `delete-folder`
Logs & deployments	`get-environment-logs`, `list-deployments`, `get-deployment`, `get-build-logs`
Variables, domains	`set-environment-variables`, `get-environment-variables`, `add-custom-domain`, `get-custom-domain-status`, `retry-custom-domain`, `remove-custom-domain`
Databases	`list-databases`, `get-database`, `create-database`, `update-database`, `delete-database`, `get-database-connection-string`, `rotate-database-password`, `get-database-schema`, `query-database`, `get-database-metrics`, `dump-database`, `import-database`
Plan & billing	`get-billing`, `list-plans`, `choose-plan`, `add-payment-method`, `payment-method-status`, `remove-payment-method`, `get-usage`, `get-usage-history`, `list-invoices`, `get-invoice`, `retry-invoice`, `get-outstanding-invoices`, `get-usage-alerts`, `set-usage-alerts`, `get-billing-details`, `set-billing-details`
Workspace & members	`create-workspace`, `list-members`, `invite-member`, `remove-member`, `set-member-role`, `list-roles`, `list-api-keys`, `create-api-key` (paid plans), `revoke-api-key`
Git providers	`get-github-installation-status`, `get-github-install-url`, `list-github-installations`, `list-repositories`, `list-branches`, `check-repo-access`, `connect-git-provider` (GitLab / Bitbucket, one link), `list-provider-repositories`
Other	`list-notifications`, `mark-notifications-read`, `contact-support`, `ping`, `get-platform-config`, `get-cloudrun-config`, and the low-level upload steps (`package-source`, `request-upload-url`, `complete-upload`, `create-application-from-upload`)

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:

Code	When	What the agent does
`DOMAIN_NOT_POINTING_HERE`	`add-custom-domain` would replace a domain that serves visitors with one whose DNS points elsewhere	Tells the user which record to add. Repeats with `force: true` only if the user says to switch anyway
`USE_DOMAIN_ROUTES`	`update-application` / `update-environment` was given a different custom domain	Uses `add-custom-domain` or `remove-custom-domain`
`PAYMENT_FAILED`	`choose-plan` charged the saved card and it was declined; the plan is unchanged	Tells the user; `add-payment-method` with `plan_id` saves a different card and switches once it is saved

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:

Variable	Default
`LIGHT_CLOUD_API_URL`	`https://api.light-cloud.com`
`LIGHT_CLOUD_CONSOLE_URL`	`https://console.light-cloud.com`

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

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

Only the beginning is shown; read the rest in the repo

Light Cloud MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

Light Cloud MCP Server

No account yet? Start here

Features

Installation

Claude Code

Claude Desktop (one-click extension)

Claude Desktop (manual config)

Usage

Available Tools

Turning agents off

Authentication

Plans and upgrading

Refusals an agent can act on

Configuration

Development

Install dependencies

Run in development mode

Build for production

Testing

License

Links

Submitting to the Anthropic directory