Build your site with an AI agent

Once your assistant is connected to Mangalyam over MCP, it can build and revise your site for you: gather the facts, pick a look, write the page, check it, and hand you a preview. This guide explains what it can do for each kind of account, how the loop works, and where the hard limits are.

If you have not connected an assistant yet, start with Connect your AI assistant.

What an agent can do

Your assistant only receives the tools that match your account. Each tool set starts with a *_site_capabilities call, which returns the live contract: the block catalog, the rules the checker enforces, and what is still missing before a site can go live. Treat that response as the source of truth — it is always more current than this page.

Couples (your private wedding site at /w/…)

• site_capabilities, site_list_photos, site_get_versions, site_list_looks
• site_lint, site_submit, site_render_preview
• site_upload_asset, couple_upload_photo, media_presign_upload, media_confirm

Vendors (your public business page at /p/…)

• vendor_get_profile, vendor_update_profile, vendor_site_capabilities, vendor_list_photos
• vendor_site_get_versions, vendor_site_submit, vendor_site_upload_asset
• site_brand_kit — derives a palette and type pairing from your logo

Agencies (your public agency page at /a/…)

• agency_get_profile, agency_update_profile, agency_site_capabilities, agency_list_showcase_photos
• agency_site_get_versions, agency_site_submit, agency_site_upload_asset

Connecting and scopes

When you approve the connection, Mangalyam shows only the scopes your account is eligible for. The assistant never sees another persona's scopes, and the server re-checks eligibility before it grants anything.

You can revoke any connection at any time from Settings → Security → Connected AI apps.

The design loop

A good agent runs the same sequence every time:

1. Capabilities. Call the *_site_capabilities tool first and read the catalog, rules and readiness list.
2. Interview or profile. For a couple, the agent asks you about the celebration and pulls photos with site_list_photos. For a business, it reads the real profile (vendor_get_profile / agency_get_profile) and proposes fixes to gaps through vendor_update_profile / agency_update_profile — it must not invent services, prices or reviews.
3. Looks. Couples choose a Site Kit look via site_list_looks; vendors can generate one from their logo with site_brand_kit. A look is applied with a single @import url(https://mangalyam.io/site-kit/<slug>.css) line.
4. Lint. site_lint returns warnings and blockers. Blockers — missing alt text, broken structure, disallowed markup — make submit refuse, so the agent fixes them before moving on.
5. Submit. The submit tool saves a draft version. Nothing is visible to anyone yet.
6. Preview. The agent can request screenshots of the draft (site_render_preview for couples) and describe what changed. You open the preview yourself at /w/preview, /p/preview or /a/preview.
7. Approve & Publish. You press the button in the browser. That step is deliberately not available to any agent.

Every submit creates a new version; *_site_get_versions lists them so you can compare or roll back.

Media

• Inline images: up to 4 MB, JPEG, PNG or WebP, sent through the site upload tools.
• Large files: up to 20 MB through the presign path — media_presign_upload returns an upload URL, the file goes straight to storage, and media_confirm attaches it.
• Invitations (couples): PNG, JPEG or PDF up to 15 MB.

Uploads count against your storage quota, and the agent can only reference media that already belongs to your account.

Privacy and indexing

• Couple sites are private. Every /w/… page is served with noindex, never appears in a sitemap, and is reachable only by people you share the link with.
• Vendor and agency sites are public marketing pages. They are indexed by search engines only after your business is approved and you have chosen to make it public. Until then they behave like private drafts.
• Photos you have opted out of showcase use are excluded both when the agent lists them and when the page renders.

What an agent can never do

• Publish. There is no MCP publish tool. An agent can draft and submit; a signed-in human must press Approve & Publish in the browser. An agent that claims it published your site is wrong.
• Invent facts. Business pages are built from your verified profile. Reviews, prices, awards or venue names that are not on file are rejected by lint or by the profile tools.
• Run scripts. Sites are HTML and CSS only — zero JavaScript. Interactive pieces such as RSVP, enquiry forms and galleries are provided as data-mangalyam widgets that Mangalyam renders on its side.
• Reach another account. Tools are scoped to the wedding or business you own; cross-account reads and writes are refused at the server.
• Bypass the checker. Submissions that fail site_lint blockers are not saved as drafts.