weegloo-web-hosting

Deploy static sites to Weegloo WebHosting via MCP upload and manage page head metadata.

1|2|Updated Feb 20, 2026
Ready to run
npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-web-hosting-weeglooapi
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: weegloo-web-hosting
Source: https://github.com/weeglooapi/weegloo-mcp-plugin/tree/main/plugins/weegloo/skills/weegloo-web-hosting
Command: npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-web-hosting-weeglooapi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a static website to Weegloo WebHosting involves several error-prone steps: choosing a unique subdomain, respecting file-count limits, packaging the build correctly, and wiring uploads to WebHosting resources through MCP tools. This Skill guides the AI through that entire flow and also covers editing a deployed page's SEO and share metadata without rebuilding or re-uploading. ## Core Features & Use Cases - Guided static deployment: Enforces static-export builds, the 300-file production cap (100 by default), and a ZIP with index.html at the root, uploaded via the CreateUpload MCP tool. - Autonomous subdomain selection: Picks a distinctive subdomain, verifies availability with CheckSubdomain, retries on collision, and reports the live *.weegloo.app URL. - Head metadata editing: Rewrites title, description, canonical, share image, favicon, and theme color through the pageMetas field of cma_UpdateOneWebHosting on MarketApp-installed hostings. - Use Case: After building a Next.js static export that integrates Weegloo content, deploy it end-to-end and later update the live site's SEO tags without a rebuild. ## Quick Start Deploy my static site build to Weegloo WebHosting and give me the live URL.

Frequently Asked Questions about weegloo-web-hosting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a static website to Weegloo WebHosting?▼

Build a static export with index.html at the root, compress it into a ZIP, upload it with the CreateUpload MCP tool, then create or update a WebHosting resource referencing that upload. Verify the subdomain with CheckSubdomain before creating the resource.

How do I change SEO meta tags on a deployed Weegloo site without redeploying?▼

Send a pageMetas array on cma_UpdateOneWebHosting with one entry per document, setting slots like title, description, image, or favicon. This works only on WebHostings installed from a MarketApp; an empty string removes a tag while omitted slots stay unchanged.

Does Weegloo WebHosting support SSR or server-side rendering?▼

No, Weegloo WebHosting serves only pre-built static files from the uploaded ZIP. SSR, server runtimes, and per-request logic are unsupported, so use static export builds and call Weegloo APIs from the browser via fetch or XHR.

What is the file limit for Weegloo WebHosting deployments?▼

Production deployments are capped at 300 archive entries after unzip, counting directories as well as files, while the code default is 100. Keeping a build at or under 100 entries is always safe, so prefer web fonts over many self-hosted font files.

Why does my Weegloo WebHosting update fail with a PENDING state error?▼

A WebHosting still in PENDING or PROCESSING state refuses further updates with error WGL422031. Poll cma_GetOneWebHosting until the resource reaches COMPLETED before sending another update.