자연어를 통해 Light Cloud Platform에서 웹 애플리케이션, API 및 데이터베이스를 배포하고 관리할 수 있도록 AI agent를 지원합니다.
다른 이름 light-cloud-com/mcp-server, @light-cloud/mcp-server
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- 878
- 최신 버전
- 1.6.2
- 마지막 커밋
- 2026년 11월 6일
- 라이선스
- MIT
Light Cloud MCP란?
Light Cloud은(는) MCP server입니다. 자연어를 통해 Light Cloud Platform에서 웹 애플리케이션, API 및 데이터베이스를 배포하고 관리할 수 있도록 AI agent를 지원합니다.
프로젝트 README에서 생성된 요약
Light Cloud MCP server 정보
이 MCP server는 Claude를 사용하는 개발자가 자연어를 통해 웹 애플리케이션, API 및 데이터베이스를 배포하고 관리할 수 있게 해줍니다. Light Cloud Platform에 대한 직접적인 인터페이스를 제공하여, 사용자가 웹 콘솔을 열지 않고도 초기 계정 설정부터 복잡한 인프라 관리까지 모든 과정을 처리할 수 있습니다. 사용자는 connect 도구를 사용하여 어떤 기기에서든 짧은 코드를 승인함으로써 가입하거나 로그인할 수 있으며, 채팅 인터페이스에 비밀번호를 입력할 필요가 없습니다.
이 server는 웹 콘솔과 동일한 기능을 제공하는 110개 이상의 도구를 제공합니다. 개발자는 upload-and-deploy를 통해 로컬 프로젝트를 배포하고, GitHub 저장소를 연결하여 자동 배포를 수행하며, 스테이징 및 프로덕션 환경을 관리하고, 스키마 검사나 SQL 쿼리와 같은 데이터베이스 작업을 처리할 수 있습니다. 또한 대화 중에 Stripe Checkout을 통해 결제 및 플랜 업그레이드를 직접 관리할 수 있습니다. 보안은 콘솔의 마스터 스위치를 통해 유지되며, 사용자는 애플리케이션 삭제나 결제 설정 수정과 같은 특정 agent 작업을 제한할 수 있습니다.
활용 사례
- 1데이터베이스 스키마 관리채팅을 통해 데이터 쿼리 또는 스키마 검사와 같은 데이터베이스 관리 작업을 수행합니다.
- 2애플리케이션 상태 모니터링런타임 로그와 환경 메트릭을 가져와 문제를 해결합니다.
- 3결제 및 업그레이드 처리대화 중에 서비스 플랜을 업그레이드하거나 결제 수단을 추가합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Light Cloud MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Light Cloud MCP 설치
$ claude mcp add mcp-server -- npx -y @light-cloud/mcp-serverCursor에 Light Cloud MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@light-cloud/mcp-server"
]
}
}
}VS Code에 Light Cloud MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@light-cloud/mcp-server"
]
}
}
}VS Code CLI에 Light Cloud MCP 설치
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@light-cloud/mcp-server"]}'Claude Desktop에 Light Cloud MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@light-cloud/mcp-server"
]
}
}
}Codex에 Light Cloud MCP 설치
$ codex mcp add mcp-server -- npx -y @light-cloud/mcp-serverCodex config.toml에 Light Cloud MCP 설치
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@light-cloud/mcp-server"]
Gemini CLI에 Light Cloud MCP 설치
$ gemini mcp add -s user mcp-server npx -- -y @light-cloud/mcp-serverGemini settings.json에 Light Cloud MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@light-cloud/mcp-server"
]
}
}
}자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능light-cloud-com/mcp-server is public and reachablegithub.com/light-cloud-com/mcp-server ↗통과
- 패키지가 이 저장소를 소스로 명시@light-cloud/mcp-server names light-cloud-com/mcp-server as sourcenpmjs.com/package/@light-cloud/mcp-server ↗통과
- 빌드 출처(Sigstore 증명)No build attestation published for this release검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-06github.com/light-cloud-com/mcp-server ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from @light-cloud/mcp-server통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음179 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기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 -
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.
Light Cloud MCP 질문
Light Cloud MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add mcp-server -- npx -y @light-cloud/mcp-server를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Light Cloud MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Claude를 사용하여 Light Cloud에 어떻게 가입하나요?
Claude에게 'Sign me up for Light Cloud as you@example.com'이라고 요청하여 가입할 수 있습니다. 기기 인증 코드를 통해 비밀번호나 신용카드 없이 무료 계정을 생성합니다.
GitHub에서 프로젝트를 직접 배포할 수 있나요?
네, 이 MCP server에는 GitHub 연동 기능이 포함되어 있어 저장소에서 직접 배포가 가능합니다.
AI agent가 수행할 수 있는 작업을 어떻게 제어하나요?
Light Cloud 콘솔의 Settings → Security → Agents & CLI 메뉴에서 agent 권한을 관리할 수 있습니다. 여기서 결제나 데이터베이스와 같은 특정 그룹에 대한 액세스 권한을 토글할 수 있습니다.