Memungkinkan AI agent untuk men-deploy dan mengelola aplikasi web, API, dan database di Light Cloud Platform melalui bahasa alami.
Juga dikenal sebagai light-cloud-com/mcp-server, @light-cloud/mcp-server
- Stars
- 0
- Tools
- —
- Unduhan, 30 hari
- 878
- Versi terbaru
- 1.6.2
- Commit terakhir
- 6 Nov 2026
- Lisensi
- MIT
Apa itu Light Cloud MCP?
Memungkinkan AI agent untuk men-deploy dan mengelola aplikasi web, API, dan database di Light Cloud Platform melalui bahasa alami.
Ringkasan dibuat dari README proyek
Tentang Light Cloud MCP server
Men-deploy dan mengelola aplikasi web, API, dan database melalui bahasa alami adalah kemampuan yang ditawarkan MCP server ini bagi developer yang menggunakan Claude. Server ini menyediakan interface langsung ke Light Cloud Platform, memungkinkan pengguna menangani segalanya mulai dari setup akun awal hingga manajemen infrastruktur yang kompleks tanpa perlu membuka web console.
Server ini menawarkan lebih dari 110 tools yang memiliki fitur setara dengan web console. Developer dapat men-deploy proyek lokal via upload-and-deploy, menghubungkan repositori GitHub untuk deployment otomatis, mengelola environment staging dan production, serta menangani operasi database seperti inspeksi schema atau query SQL. Server ini juga mengelola billing dan upgrade plan melalui Stripe Checkout langsung di dalam percakapan. Keamanan tetap terjaga melalui master switch di konsol yang memungkinkan pengguna membatasi tindakan agent tertentu, seperti menghapus aplikasi atau mengubah pengaturan billing.
Apa yang bisa Anda lakukan dengannya
- 1Kelola database schemaLakukan tugas administrasi database seperti melakukan query data atau menginspeksi schema melalui chat.
- 2Monitor kesehatan aplikasiAmbil runtime logs dan metrik environment untuk troubleshooting masalah.
- 3Tangani billing dan upgradeUpgrade plan layanan Anda atau tambahkan metode pembayaran selama percakapan berlangsung.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Light Cloud MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Light Cloud MCP di Claude Code
$ claude mcp add mcp-server -- npx -y @light-cloud/mcp-serverInstal Light Cloud MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@light-cloud/mcp-server"
]
}
}
}Instal Light Cloud MCP di VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@light-cloud/mcp-server"
]
}
}
}Instal Light Cloud MCP di VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@light-cloud/mcp-server"]}'Instal Light Cloud MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@light-cloud/mcp-server"
]
}
}
}Instal Light Cloud MCP di Codex
$ codex mcp add mcp-server -- npx -y @light-cloud/mcp-serverInstal Light Cloud MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@light-cloud/mcp-server"]
Instal Light Cloud MCP di Gemini CLI
$ gemini mcp add -s user mcp-server npx -- -y @light-cloud/mcp-serverInstal Light Cloud MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@light-cloud/mcp-server"
]
}
}
}Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkaulight-cloud-com/mcp-server is public and reachablegithub.com/light-cloud-com/mcp-server ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernya@light-cloud/mcp-server names light-cloud-com/mcp-server as sourcenpmjs.com/package/@light-cloud/mcp-server ↗Lolos
- Provenance build (atestasi Sigstore)No build attestation published for this releaseTidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-06github.com/light-cloud-com/mcp-server ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from @light-cloud/mcp-serverLolos
- Tidak ada advisory kritis pada paket atau dependensinya179 resolved dependencies checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubLight 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 -
connectwith 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 -
passwordon 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-<version>.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-<version>.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
Links
Submitting to the Anthropic directory
What the Software Directory policy asks for and where it is:
- Bundle: the
.mcpbon the latest release; source in this repository. - Tool annotations (
title,readOnlyHint,destructiveHint) on every tool; descriptions match behaviour; no hidden instructions. - Privacy policy: https://www.light-cloud.com/legal/privacy-policy · support: https://www.light-cloud.com/contact · docs: https://docs.light-cloud.com/deploy-with-ai/mcp-server
- Example prompts: "Connect me to Light Cloud as you@example.com", "Deploy this project to Light Cloud", "Add a Postgres database and set DATABASE_URL on production", "Why did the last deployment fail? Check the logs".
- Test account with sample data: provided on the submission form.
Pertanyaan tentang Light Cloud MCP
Bagaimana cara menambahkan Light Cloud MCP ke Claude Code?
Jalankan claude mcp add mcp-server -- npx -y @light-cloud/mcp-server di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Light Cloud MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Bagaimana cara mendaftar Light Cloud menggunakan Claude?
Anda bisa mendaftar dengan meminta Claude untuk 'Sign me up for Light Cloud as you@example.com'. Ini akan membuat akun gratis tanpa perlu password atau kartu kredit melalui kode otorisasi perangkat.
Bisakah saya men-deploy proyek langsung dari GitHub?
Ya, MCP server ini menyertakan integrasi GitHub yang memungkinkan Anda men-deploy langsung dari repositori Anda.
Bagaimana cara mengontrol apa yang boleh dilakukan oleh AI agent saya?
Anda dapat mengelola izin agent di konsol Light Cloud melalui Settings → Security → Agents & CLI, di mana Anda bisa mengaktifkan atau menonaktifkan akses untuk grup spesifik seperti billing atau database.