This website was built and published over MCP
Every block on this page was created by an agent calling the marketing-website generator's Model Context Protocol server — no dashboard clicks, no hand-written HTML.
Authored entirely by tool calls
Block-based
create_page + save_page emit typed blocks (hero, features, faq, cta…) validated by the same schema the visual editor uses.
RBAC-scoped
The MCP token authenticates as an operator; every tool reuses the app's role checks, so an agent can only touch sites it may access.
Git-backed
save_page commits to the client's git repo — the source of truth. Postgres is just a read index.
Themed
set_theme and set_chrome drive colors, fonts and the header/footer around every page.
One-call publish
publish_site renders a static artifact and atomically swaps it live behind auto-HTTPS.
Custom domain
This page is served at demo-mcp.bitgeek.in from the published static build.
The flow, end to end
- list_clients to find the client
- create_site seeds a home page
- describe_blocks then save_page to author content
- set_theme / set_menus / set_chrome for polish
- publish_site builds and goes live
That is exactly the sequence that produced the page you are reading.
Video, too
The embed widget renders trusted-provider video — here Big Buck Bunny, a Creative Commons (CC BY) open movie by the Blender Foundation.
Questions
Was any of this page written by hand?
No. The content came from MCP tool calls against the published server; only the deploy plumbing (DNS, Caddy) was operator-side.
Can it be edited in the dashboard too?
Yes — MCP and the visual editor share one block schema and one git history, so either can pick up where the other left off.
How is it served?
publish_site writes a static build; the host map symlinks demo-mcp.bitgeek.in at the latest build and Caddy serves it over the *.bitgeek.in wildcard certificate.
Built by an agent, in one session.
The same tools are available to any MCP client pointed at this control plane.