Run Your Whole Site From Inside Claude.ai

Most website tools split into two worlds: a builder for setup, a dashboard for operations. Sitelas collapses both into a Claude.ai chat. Here's what that actually looks like.

What ships in the connector

Sitelas exposes its whole feature set to Claude.ai as MCP tools, over OAuth 2.1. Once installed, every feature in the product becomes a Claude verb — site creation, content editing, brand changes, scheduled publishing, form submissions, contact records, analytics, and custom domains. Site creation and editing run on Claude's own tokens via your claude.ai subscription; Sitelas charges zero AI credits on this path.

Installation (one minute)

1. Add Sitelas from Claude's connector directory — one click.
2. On Claude Code or Claude Desktop, which read a config file instead, use https://sitelas.com/api/mcp.
3. Sign in to Sitelas when prompted. PKCE-protected OAuth 2.1 — 1-hour access tokens, 30-day refresh tokens that rotate on every use.

Day 0: Site creation

"Build a bakery site for Midnight Oven, Brooklyn — sourdough plus coffee, warm palette, contact-only."

Claude calls select_template_for_brief with structured arguments (audience, register, conversion goal). The tool returns the top three scored archetypes. Claude picks one, clones it via create_site_from_template, then runs bulk passes — patch_nodes for copy, replace_images_from_search for hero shots. Live at midnight-oven.sitelas.com in about a minute.

Day 3: Submissions and contacts

"Anyone reach out this week?"

Claude calls list_submissions — three messages. Sarah asks about gluten-free; Mike wants catering. "Draft a reply to Mike about Saturday catering." Claude calls draft_reply_to_submission; the draft lands in your dashboard inbox ready to send.

Day 5: Analytics

"How's traffic been?"

Claude calls get_analytics(range_days: 7) and top_pages. You get pageviews, unique sessions, top paths, top referrers, and a daily timeseries — in chat. No dashboard tab needed.

Day 7: Scheduled publishing

"Publish a 'Closed Thursday' banner next Wednesday at 9am."

Claude calls schedule_publish with a banner-bar patch and a future run_at. A Vercel cron flips the live page over at the scheduled time.

Day 21: Cloning a layout

"Clone the layout of ra.co and adapt it for my warehouse-party series."

Claude calls capture_url — a Fly.io Playwright service returns a full-page screenshot, simplified DOM, and detected brand tokens. Claude's vision reads the screenshot, picks the closest events-category archetype, and composes a replica in-session.

What's intentionally not in the connector

Stripe Connect (we don't touch the money), native commerce or bookings (use stripe-payment-link and calendly-embed instead), broadcast email sending (use Mailchimp / ConvertKit / Beehiiv directly). Anything Claude already has a native connector for — Gmail, Drive, Calendar, Microsoft 365 — Sitelas leaves alone; it shows up as a verb-rich endpoint those existing connectors can call into.

One subscription, two surfaces

You can also build and edit from yourname.sitelas.com/edit with the in-editor AI chat (Gemini 2.5 Pro). It calls the same MCP tools Claude does — same fixture, same authoring layer. Same site, just a different chat panel.