Help & quickstart

LandingConnect deploys static sites from Claude Cowork or Claude Code to <you>.landingconnect.com, with automatic SSL on your own domain.

What you can build

Just tell Claude what you want — it asks a few simple questions, builds the pages, and publishes them. Three common starting points:

• Clone an existing site — move off WordPress or paid hosting onto fast static HTML you update by chatting. Try: “Copy beachcliffassociation.com into a LandingConnect site I can edit here.”
• Improve your site — modernize the look, copy, and speed of what you already have. Try: “Make my site better and more modern: example.com”
• Build something new — start from scratch. Try: “Build me a landing page for my coffee shop.”
• Share a report or doc — publish content Claude writes as a link instead of an attachment, kept unlisted or password-protected. Try: “Publish this report as a private link I can send to my client.”

For clone and improve, the connector fetches your real page server-side (site_import_url) so Claude works from the actual source, then generates the files and deploys.

1. Deploy your first site (≈2 minutes)

1. In Cowork or Claude Code, add the connector: https://connect.landingconnect.com/mcp
2. When prompted, click Connect / Authorize — your client opens a browser to sign in to LandingConnect once. After that it stays connected (no codes to copy).
3. Tell it: “deploy my site to <name>”. The reliable path is inline files (the connector sends each file directly — no upload step), so it works even in sandboxed environments.
4. Your site goes live at <name>-xxxx.landingconnect.com. A clean, no-suffix “vanity” name is a Pro perk.

Updating & rolling back

Change your site and redeploy through the connector — the URL never changes, SSL stays automatic, and every deploy is versioned. Roll back to any previous version in one click from the site’s Overview.

Custom domains

On a site’s Overview, add a custom domain. Point a CNAME at edge.landingconnect.com (DNS-only, no proxy) and SSL is issued automatically within a minute or two. Watch it progress with domain_status.

Analytics

The Analytics tab shows requests over time, top pages, referrers, countries, status mix, and bandwidth — privacy-friendly and aggregate, updated within ~15 seconds. No cross-site tracking.

Visibility, password & robots

On the Settings tab, choose Public (indexed), Unlisted (link-only, not indexed — the default), or Private (password required). Toggle search engines and AI crawlers independently. The platform generates your robots.txt from these. You can also set this straight from chat — “make this report private with a password” calls site_set_visibility.

Connector tools

• account_whoami — show your account, plan, and usage.
• site_import_url — fetch a public page (to clone or improve) so Claude works from the real source.
• site_create / site_list / site_deploy / site_status / site_logs / site_rollback / site_set_visibility.
• share_invite / share_list / share_revoke — invite collaborators to a site.
• domain_add_custom / domain_status / domain_verify.
• seo_audit / seo_tips / troubleshoot.

FAQ

Does it work in plain Claude chat? Yes — for hand-written pages, Claude writes the files and deploys via the inline path. Cowork/Claude Code are needed when there’s a real build step or binary assets.

How many sites can I make? As many as you want — everything is unlocked during early access.

Troubleshooting

Run troubleshoot from the connector for a diagnostic battery (deploy present? files on disk? DNS resolves? cert issued?). A 404 right after deploy usually means there’s no index.html at the site root.