Official
Run `fly mcp server` to expose flyctl operations to AI agents.
fly-io, hosting, flyctl, edge
MCPs to Launch a Website End to End
Getting a site live crosses three categories: buy the name, build the pages, put it on a host. This collection gathers every ranked server in domains, website builders and web hosting in one place, so an agent asked to "register this and put the site up" can see the whole chain at once. Most setups need two or three of these; Hostinger is the one that covers all three from a single credential.
20 MCPs in this collection
Top Launch a Website MCPs ranked
Popularity-ordered. Click any card for install snippets, fact sheet, and trust signals.
Official
Reach the whole Cloudflare API from an agent — DNS records, Workers, R2, and the Registrar beta — through one hosted Code Mode server.
cloudflare, edge, workers, dns
Official
Provision Render services, read deploy logs and metrics, and query Postgres read-only — over a hosted OAuth MCP.
render, web-hosting, deployment, paas
Buy a domain, provision hosting, deploy a site, and set its DNS — one official server covering the whole chain, now through three search-and-execute tools.
hostinger, domains, web-hosting, dns
Official
Manage Droplets, App Platform, Kubernetes, and Spaces from an AI agent.
digitalocean, hosting, cloud, kubernetes
Official
Deploy a site, read the build, and manage projects, forms and extensions with Netlify's official MCP server.
netlify, web-hosting, deployment, jamstack
Official
Manage Heroku apps, dynos, add-ons, and Postgres from an AI agent.
heroku, hosting, paas, postgres
Official
Model, write and publish structured content from an agent — 73 tools across entries, assets and content types.
contentful, cms, headless-cms, website-builders
Official
Query and edit Sanity content over a remote OAuth MCP — no token in a config file.
sanity, cms, headless-cms, groq
Official
Edit a live Webflow site from an agent — CMS collections, pages, and the Designer canvas over OAuth.
webflow, website-builders, cms, no-code
Diagnose a domain before and after you change it — DNS, DNSSEC, SPF, DKIM, DMARC, TLS — with no API key.
intodns, dns, dnssec, spf
Register, transfer and manage Name.com domains and DNS from an agent — the official server, sandboxed by default.
name-com, domains, registrar, dns
Deploy to your own server from an agent — the self-hosted answer to Vercel and Railway.
coolify, web-hosting, self-hosted, deployment
Publish and manage a WordPress site from an agent over the REST API — posts, pages, media, plugins, themes.
wordpress, cms, website-builders, publishing
Deploy from files or Git, buy and attach domains, edit DNS, and debug deployments on Vercel — the official remote MCP, over OAuth.
vercel, hosting, deployment, domains
Draft, schedule and publish to Ghost with a preview-then-approve gate on every write.
ghost, cms, publishing, blogging
Official
Spin up Railway projects, services, and deploys via remote MCP with OAuth.
railway, hosting, deployment, paas
2 minLow
At-cost registration and full DNS control from an agent — read-only until you explicitly turn writes on.
porkbun, domains, registrar, dns
Read and edit a Namecheap portfolio from any MCP client — the non-ChatGPT path to the same account.
namecheap, domains, dns, registrar
Self-hosted CMS content and schema editing from an agent — 20 tools including content-type creation.
strapi, cms, headless-cms, self-hosted
FAQ: Launch a Website
How many MCP servers do I actually need to launch a site?
Usually two or three: one that owns the domain and its DNS, one that owns the pages, and one that owns the deploy. A common shape is Cloudflare for DNS, a CMS or builder for the content, and Vercel or Netlify for hosting. Hostinger is the exception — it registers, writes DNS, provisions hosting and deploys from one server, which is simpler to set up and a wider blast radius if the credential leaks.
What order should the agent do things in?
Check availability and register the name first, because everything else depends on it and it is the only step that can fail for reasons money cannot fix. Then create the site or content. Then deploy. Point the DNS last, once there is something live to point at — a record aimed at a dead host caches badly. Verify afterwards with a DNS diagnostic server rather than by re-reading the record you just wrote.
Which steps should stay behind a human confirmation?
Three: registering a domain (it spends money and the name is yours either way), promoting anything to production (there is no preview step on most builders — publishing is what visitors see), and any full-replace write. Zone-replace and environment-variable-replace tools delete whatever you did not send, which is the quietest way an agent breaks a working site.
Can an agent do this with no human in the loop at all?
Technically yes, and it is worth being careful about. The servers that make it safest are the ones that gate writes structurally rather than by prompt: Porkbun starts read-only and needs two flags before it can register, Ghost requires a preview hash plus an explicit confirmation on every write, and Name.com defaults to a test environment. Prove the whole chain against those first.