Clutch for IT and security

What Clutch runs in production is HTML.

A site is one document of components, rendered to HTML with no framework runtime and served from Cloudflare Workers and R2.

View source

A published Clutch site serves plain markup you can read in view-source.

Real render output of the Larkspur Commons template, captured once on 23 Oct 2026. Never mocked.

Larkspur Commons' home page, then its source: plain HTML with a JSON-LD block naming the ApartmentComplex, its telephone and address, and a module script that registers the page's WebMCP tools; then the body's headings, the search form with its labels, the rent and the tour form.

Connections

Any tool you already run can connect to Clutch over MCP.

MCP is a standard that lets an AI agent or a ticketing tool work with another tool. Clutch's server uses OAuth.

A pine brick settling onto a stack of slabs: your tools connect over MCP

Nothing on a Clutch site ships without a person pressing Publish.

Only the marketer publishes

The agent prepares a draft and never publishes it.

Writes are JSON Patches

The agent writes no code. Every write is a JSON Patch (RFC 6902) to one document, versioned per write.

Every publish is graded

Publish grades the changed pages on find, understand, act and performance, and fixes what the document owns first.

One DNS change

One CNAME record per hostname; hosting and SSL sit on Clutch's side of the switch.

Answers from the page

Find ranks passages from the page; a question it cannot answer is an error, never an invention.

Rollback is a version

Restore returns the draft to any earlier version, and the later versions are kept.

Clutch answers three IT questions in writing, not on this page.

  • Content export if the contract endsOpen
  • Who owns the document and the mediaOpen
  • What happens to the sites if Clutch disappearsOpen
Ask us in writing and get a written answer

Clutch's grader names each miss in your markup.