Connections
Clutch works from the tools you use
Change your site from Claude, ChatGPT or your own agents over MCP. Sheets, Drive, GA4, Figma and Google Places connect too.
Claude, beside Larkspur Commons' draft floor plans. Someone asks Claude to add the November special to every floor plan page. Claude uses Clutch over MCP: list_sites, then ask_site; Clutch's card says the draft is updating and publish waits in Clutch. On the right, each plan's offer line fills: November, one month free on a 13-month lease.
Clutch connects to your AI assistants, spreadsheets, analytics and design files.
Your agents, over MCP
Claude, ChatGPT and your own agents sign in once, then ask a site for a change or publish.
Data and design files
Sheets, Drive, GA4, Figma and Places. A list can read from a connected sheet; the agent reads GA4 too.
Fifty sites, one request
Each draft is graded and fixed first; a site whose agent is still working is refused rather than forced.
50
The product's own limit, Oct 2026
Clutch is the building and hosting engine in your stack,
and the rest of the stack stays yours.- ClutchBuilds and hosts the site
- Your agentAsks for the change
- Your sheetHolds the list a visitor sees
- Your analyticsReads beside the site's own count
Clutch changes connected data only when you ask.
Every site in a workspace shares its connections.
Connected data is read; it is changed only when you asked for that in the same message.
The connections named here are the ones in the code; Slack and any property management system are not among them.