From zeabur
Creates Zeabur projects by listing user servers for region selection, retrieves project IDs via jq, and deploys templates with npx Zeabur CLI. Useful for new project and environment setups.
npx claudepluginhub zeabur/agent-skills --plugin zeaburThis skill uses the workspace's default tool permissions.
> **Always use `npx zeabur@latest` to invoke Zeabur CLI.** Never use `zeabur` directly or any other installation method. If `npx` is not available, install Node.js first.
Deploys local projects or GitHub repos to Zeabur via CLI. Manages project selection, direct deploys (default), and Git-based methods. Activates on 'deploy this', 'deploy to Zeabur', or repo search requests.
Deploys apps to Render by analyzing codebases, generating render.yaml blueprints, and providing dashboard deeplinks. For Git-backed services, Docker images, databases, and cron jobs.
Deploys Git-backed apps to Render by analyzing codebases, generating render.yaml blueprints, creating services via MCP, and providing dashboard deeplinks. Use for hosting on Render.
Share bugs, ideas, or general feedback.
Always use
npx zeabur@latestto invoke Zeabur CLI. Never usezeaburdirectly or any other installation method. Ifnpxis not available, install Node.js first.
Do NOT hardcode or guess region codes. Old region codes like hnd1, tpe1 are deprecated. The region must always be derived from the user's server list.
Step 1 — List the user's servers:
npx zeabur@latest server list -i=false --json
Step 2 — Ask the user which server to use:
Present the server list to the user (show name, provider, and region for each) and ask them to pick one. Do NOT choose a server on the user's behalf. Also offer the option to rent a new server if none of the existing ones are suitable.
zeabur-server-catalog skill to browse options, then the zeabur-server-rent skill to rent one.Step 3 — Use the selected server ID with server- prefix as the region:
The region code format is server-<server-id>, where <server-id> comes from the server list output.
Some templates (e.g. with
REQUIRE_DEDICATED_SERVER) can only be deployed on dedicated servers. If you getUnsupported template (code: REQUIRE_DEDICATED_SERVER), rent a dedicated server and recreate the project with its region.
# Create project with name and region (region must be server-<server-id>)
npx zeabur@latest project create -n "<project-name>" -r "server-<server-id>" -i=false --json
# List projects as JSON and extract project ID by name
PROJECT_ID=$(npx zeabur@latest project list -i=false --json | jq -r '.[] | select(.name == "<project-name>") | ._id')
# Deploy template file to specific project (non-interactive)
npx zeabur@latest template deploy -i=false --json \
-f <template-file> \
--project-id <project-id> \
--var PUBLIC_DOMAIN=myapp \
--var KEY=value
# 1. Find server ID
npx zeabur@latest server list -i=false --json
# 2. Create project (use server-<id> from step 1)
npx zeabur@latest project create -n "wrenai-prod" -r "server-<server-id>" -i=false --json
# 3. Get project ID
PROJECT_ID=$(npx zeabur@latest project list -i=false --json | jq -r '.[] | select(.name == "wrenai-prod") | ._id')
echo "Project ID: $PROJECT_ID"
echo "Dashboard: https://zeabur.com/projects/$PROJECT_ID"
# 4. Deploy template — use the `zeabur-template-deploy` skill for detailed flags and troubleshooting
npx zeabur@latest template deploy -i=false --json -f template.yml --project-id $PROJECT_ID --var PUBLIC_DOMAIN=myapp