팀과 코딩 에이전트를 위해 Docker Compose 파일 기반의 셀프 호스팅 프리뷰 환경을 관리합니다.
다른 이름 Flosk6/Spawner, spawner-cli
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 13일
- 라이선스
- Apache-2.0
Spawner MCP란?
Spawner은(는) MCP server입니다. 팀과 코딩 에이전트를 위해 Docker Compose 파일 기반의 셀프 호스팅 프리뷰 환경을 관리합니다.
프로젝트 README에서 생성된 요약
Spawner MCP server 정보
Spawner는 소프트웨어 팀과 코딩 에이전트를 위한 셀프 호스팅 프리뷰 환경 관리를 지원합니다. 기존 Docker Compose 파일을 사용하여 모든 git branch에 대해 애플리케이션의 일시적인 복사본을 생성하며, 각 환경에 전용 URL, 데이터베이스 및 로그를 제공합니다. 이 시스템은 Kubernetes 없이 자체 서버에서 실행되므로, 격리된 테스트 공간이 필요한 개발자에게 가벼운 대안이 됩니다.
사용자는 웹 대시보드, CLI 또는 Claude Code, Codex, Cursor와 같은 클라이언트를 위해 설계된 MCP server를 통해 시스템과 상호작용합니다. 설정을 위해서는 Docker가 설치된 Ubuntu 또는 Debian 기반의 전용 서버와 와일드카드 DNS 레코드가 필요합니다. 환경 관리를 위해 spawner_up, spawner_logs, spawner_exec와 같은 도구를 사용합니다. 리소스 절약을 위해 시스템은 사용하지 않는 환경을 자동으로 휴면 상태로 전환하며, 디스크 사용량을 최소화하기 위해 공유 레이어를 사용합니다.
활용 사례
- 1브랜치 프리뷰 배포AI 에이전트가 로컬 워크트리에서 전체 애플리케이션 스택을 실행하여 커밋되지 않은 변경 사항을 테스트할 수 있습니다.
- 2서비스 오류 디버깅개발자가 실행 중인 컨테이너에서 특정 오류 로그와 스택 트레이스를 가져와 충돌 문제를 해결할 수 있습니다.
- 3원격 명령 실행프리뷰 환경 내의 특정 서비스에서 데이터베이스 마이그레이션이나 기타 터미널 명령을 직접 실행할 수 있습니다.
- 4일시적 링크 공유이해관계자가 정식 계정 없이도 프리뷰를 확인할 수 있도록 임시 액세스 링크를 생성할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Spawner MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Spawner MCP 설치
$ claude mcp add spawner -- npx -y spawner-cliCursor에 Spawner MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"spawner": {
"command": "npx",
"args": [
"-y",
"spawner-cli"
]
}
}
}VS Code에 Spawner MCP 설치
.vscode/mcp.json
{
"servers": {
"spawner": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"spawner-cli"
]
}
}
}VS Code CLI에 Spawner MCP 설치
$ code --add-mcp '{"name":"spawner","type":"stdio","command":"npx","args":["-y","spawner-cli"]}'Claude Desktop에 Spawner MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"spawner": {
"command": "npx",
"args": [
"-y",
"spawner-cli"
]
}
}
}Codex에 Spawner MCP 설치
$ codex mcp add spawner -- npx -y spawner-cliCodex config.toml에 Spawner MCP 설치
~/.codex/config.toml
[mcp_servers.spawner] command = "npx" args = ["-y", "spawner-cli"]
Gemini CLI에 Spawner MCP 설치
$ gemini mcp add -s user spawner npx -- -y spawner-cliGemini settings.json에 Spawner MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"spawner": {
"command": "npx",
"args": [
"-y",
"spawner-cli"
]
}
}
}자동 검사
2026년 11월 15일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능flosk6/spawner is public and reachablegithub.com/flosk6/spawner ↗통과
- 패키지가 이 저장소를 소스로 명시spawner-cli names flosk6/spawner as sourcenpmjs.com/package/spawner-cli ↗통과
- 빌드 출처(Sigstore 증명)Sigstore attestation for spawner-clinpmjs.com/package/spawner-cli/v/2.2.1#provenance ↗통과
- 오픈 소스 라이선스 (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-12github.com/flosk6/spawner ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from spawner-cli통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기Spawner
Spawner is an open source, self-hosted preview environment manager: a copy of your app for each git branch, on your own server, with its own URLs, database and logs, for teams and their coding agents.
Website · Documentation · Compare · Changelog · Releases · npm
Spawner builds preview environments (also called review apps or ephemeral environments) from your project's Docker Compose file, without Kubernetes. Developers, reviewers and coding agents start one from a branch, or from a worktree with its uncommitted changes, then open it, run commands in it, read its logs, share it and delete it. Environments nobody uses go to sleep, so many fit on one server. Free under Apache-2.0.
Status: out of beta since 2.1.0. Only the latest release gets fixes, and the dashboard updates a server in one click.
$ cd ~/code/blog-feat-login # an agent's worktree, branch feat/login
$ spawner up --wait
feat-login (blog) is ready
web https://feat-login--blog.preview.example.com
api https://api--feat-login--blog.preview.example.com
$ spawner exec -i feat-login db -- mysql -uapp -papp app < fixtures.sql
$ spawner logs feat-login api --errors
$ spawner share feat-login # a link for someone without an account
$ spawner down feat-login
Quick start
On a server dedicated to previews (Ubuntu 22.04 or 24.04, Debian 12, amd64 or arm64; at least 4 GiB of memory, 8 GiB or more advised), with a DNS record *.preview.example.com pointing to it:
curl -fsSL https://github.com/Flosk6/Spawner/releases/latest/download/install.sh | sudo bash
The installer asks for the domain, an e-mail and your DNS provider (for one wildcard certificate), installs Docker if needed, starts Spawner, and prints the link that creates the first admin account. Then, on your machine (Node.js 20 or later), in a project:
npm install -g spawner-cli
spawner login https://spawner.preview.example.com
spawner init
spawner init writes .spawner/ (a manifest and a Docker Compose file, to adjust), offers to add the instructions for coding agents, and prints the project's slug. An admin adds the project in the dashboard (Projects, New project): that slug, the repository, and the directory of .spawner/ in a monorepo. Then spawner up --wait starts the environment of the branch. The quick start goes through each step, and the examples (Node.js and PostgreSQL; Laravel, Next.js and MySQL) are ready to deploy.
How it works
flowchart LR
clients["browser, agent, CLI"] --> traefik["Traefik on *.preview.example.com"]
traefik --> spawner["spawner.preview.example.com<br>dashboard and API"]
traefik -.->|"checks access to protected URLs"| spawner
traefik --> env1["feat-login--blog.preview.example.com<br>web, api, db on their own network"]
traefik --> env2["main--blog.preview.example.com<br>web, api, db on their own network"]
A project describes its environment in its repository, in .spawner/: a manifest that names its URLs and its seed, and a regular Docker Compose file.
# .spawner/spawner.yaml
version: 1
project: blog
exposures:
- { name: web, service: web, port: 3000 }
- { name: api, service: api, port: 8000 }
seed:
- { service: api, run: [php, artisan, migrate, --seed, --force] }
For each environment, Spawner checks out the branch or receives the worktree, checks the compose file against a security policy, builds and starts it on its own Docker network, seeds it, and routes its URLs through Traefik with HTTPS. Updates keep the data. Every change is a job with a live log, whether it comes from the dashboard, the CLI, the MCP server or the API.
For coding agents
An agent tests its own work in a real environment, from its worktree, without pushing:
spawner up --wait --json: commands print JSON with--jsonand exit with stable codes (4: the environment failed, with the end of the build log; 6: quota or capacity reached; 7:.spawner/refused, with what to fix);spawner url --with-tokengives the header that opens protected URLs, for curl or Playwright;spawner execruns a command in any service;spawner logs --errorskeeps the error lines, stack traces whole;spawner statussays which service crashed and why;spawner mcpis an MCP server for Claude Code, Codex, Cursor and other clients (claude mcp add spawner -- spawner mcp), with nine tools:spawner_up,spawner_status,spawner_list,spawner_logs,spawner_exec,spawner_stats,spawner_url,spawner_shareandspawner_down;- each agent on its own branch gets its own environment and database; agents deploying at once do not get in each other's way.
See coding agents and the CLI.
Many environments on one server
- Sleep: after 2 hours (by default) without a visit or an action, an environment's containers stop; the next visit to a protected URL wakes it up within seconds.
- Shared layers: environments share their base images and dependencies; each one only adds its code and build output (about 4 MiB for the Laravel example). Spawner warns about Dockerfiles that prevent it: see making environments cheap.
- Capacity: Spawner says how many more environments of each project fit, from what they really use, and refuses one that does not fit.
- Lifetime and quotas: by default, environments expire after 72 hours unless someone deploys them again, and each person may own 5. Spawner cleans up what deleted environments leave, and nothing else.
Supervision
Each environment has its logs (by service, errors only, live), the CPU and memory of each service over time, its disk, a timeline of crashes, out-of-memory kills and failing healthchecks, and a terminal into any service; a deleted one stays readable for 7 days. Admins see the server: alerts, 30 days of history, every container, and how many more environments fit.
Security
Branches run unreviewed code: compose files are checked against an allowlist (no host mounts, privileged containers, host network or Docker socket), each environment has its own network, Traefik has no Docker socket, and the server is meant for previews only. Accounts have no passwords (invitations and passkeys, GitHub optional); tokens have scopes and expiries; previews are protected by default, and Spawner's cookies never reach the applications. An audit trail records who did what. No telemetry: on its own, Spawner only asks GitHub for new releases (SPAWNER_UPDATE_CHECK=false turns that off). See security.
What Spawner does not do
One installation runs previews on one server, from Docker Compose: no production, no Kubernetes, no cluster, and no environment opened by itself for a pull request (CI calls spawner up, see the CI guide). See the whole list, and the comparison with other tools.
Documentation
- Quick start: from a fresh install to the first environment
- Installing: requirements, DNS providers, options, upgrades, removal
- Concepts: projects, environments, jobs, lifecycle, access, limits
- The manifest:
.spawner/, its rules, and what makes environments cheap - The CLI and the MCP server: commands, JSON outputs, exit codes, MCP tools
- Coding agents: Claude Code, Codex, Cursor
- Pull requests in CI: previews from GitHub Actions and GitLab CI
- Examples and troubleshooting
- Security, operations (backups, disk, monitoring), configuration (every setting)
- Architecture: how Spawner is built, for contributors
Development
apps/
├── api/ NestJS, Prisma (PostgreSQL): the API and the environment engine
├── cli/ The spawner CLI and MCP server, bundled into one file
└── web/ Vue 3, Vite, Tailwind CSS, PrimeVue
packages/
├── core/ Manifest, compose policy and rendering (pure, shared with the CLI)
├── types/ API types shared by the web app and the CLI
└── utils/ Git input validators
examples/ Projects ready to deploy
scripts/ End-to-end tests, the capacity check, the release
Requirements: Docker with Compose v2, Node.js 22 and pnpm 8.
pnpm install && pnpm build
cp .env.example .env # set SPAWNER_DATA_DIR to an absolute path
docker compose up -d --build # Postgres, Traefik, Spawner: http://spawner.localtest.me
docker logs spawner # the link that creates the first admin account
pnpm dev # or the API on :3000, the web app on :8080, hot reload
pnpm lint && pnpm typecheck && pnpm test
scripts/e2e-engine.sh # end to end: a local stack, the API, the CLI and MCP
Every subdomain of localtest.me resolves to 127.0.0.1. Over plain HTTP, browsers allow passkeys on localhost only: a local install lets invitations log in without one. See scripts for the tests.
Contributing
Issues are welcome: bugs, questions and ideas. Pull requests from outside are not accepted for now; see contributing. Report vulnerabilities privately: security policy.
License
Apache-2.0: free to use, modify and distribute, commercially too. Copyright 2025-2026 Flosk6.
Spawner MCP 질문
Spawner MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add spawner -- npx -y spawner-cli를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Spawner MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Spawner란 무엇인가요?
Spawner는 자체 서버에서 각 git branch마다 앱의 복사본을 생성하는 오픈 소스 셀프 호스팅 프리뷰 환경 관리 도구입니다.
Spawner를 사용하려면 Kubernetes가 필요한가요?
아니요, Spawner는 Kubernetes 없이 프로젝트의 Docker Compose 파일을 사용하여 프리뷰 환경을 구축합니다.
코딩 에이전트가 Spawner를 사용할 수 있나요?
네, Spawner는 Claude Code, Codex, Cursor와 같은 코딩 에이전트가 환경을 관리할 수 있도록 전용 MCP server를 제공합니다.