Best MCP Servers for Building Websites in 2026 (Builders + CMS)
The best MCP server for building a website is WordPress if the site already runs there (200 verified tools over the REST API), Webflow if you want an agent that can edit the design and not only the content, Wix if the site does not exist yet and you want one generated from a sentence, and Contentful or Sanity if your own front end renders the pages. Below: ranked picks with the tool counts we measured, a decision tree, and the two vendor servers that look like site editors and are not.
The question that decides everything: who renders the page?
Two very different kinds of server sit in this category, and picking the wrong kind wastes an afternoon. Page-owning builders — WordPress, Webflow, Wix, Hostinger — render the page themselves. When the agent publishes, visitors see the change immediately; there is no build step and no deploy. Headless CMS platforms — Contentful, Sanity, Strapi, and Ghost when it fronts a static site — hold structured content that some other front end renders. Publishing there is a content event; getting it onto the page is a separate deploy.
That distinction drives the guardrails too. On a builder, the dangerous tools are the ones that change what visitors see with no preview — theme activation, publish, page delete. On a headless CMS, the dangerous tools are the ones that change the model: deleting a content type takes its entries with it, and no amount of front-end caution helps.
Setup time
5–10 min per platform
Risk profile
Drafts are cheap; publish and delete are not
Cost
MCPs are free; the platforms are not
Two vendor MCPs look like site editors and are not
@wix/mcp npm package exposes twelve tools, every one of them a search over Wix documentation. Shopify's official @shopify/dev-mcp exposes six, all documentation search and code validation. We ran both and read the tool lists back. They are good at what they do — keeping an agent on the current API version instead of the one it memorised — but an agent handed either will explain confidently what it would change and change nothing. Wix site generation runs through the ChatGPT App.Decision tree — which builder or CMS MCP for which job
Pick by the platform that already owns the site. Only pick by preference when there is no site yet.
| If you… | Install | Why |
|---|---|---|
| The site already runs on WordPress | WordPress REST MCP | 200 verified tools over the REST API with an application password. Multi-site: list_sites first, then a site argument on everything. |
| The site runs on Webflow and the agent should touch the design too | Webflow | Official remote MCP over OAuth, plus a Designer bridge app that reaches the canvas, not only the CMS record. |
| The site does not exist yet and you want one from a brief | Wix (ChatGPT App) | The only entry that generates pages, copy and layout from one sentence. ChatGPT-only; the @wix/mcp npm package is docs search, not this. |
| Structured content behind your own front end, with publish workflows | Contentful | 73 verified tools, and the only one that edits the content model — create a content type, configure its editor interface — not just the entries. |
| Structured content you want to query by shape rather than by page | Sanity | Hosted OAuth endpoint, no token to store. GROQ means "every post referencing this author" is a query, not a paging loop. |
| A publishing workflow where nothing should go live unreviewed | Ghost | Preview returns a site-bound hash; apply refuses without it. Every write needs user_confirmed=true. |
| The CMS has to run on your own infrastructure | Strapi | Self-hosted, and its schema tools can scaffold a content type and populate it in the same session. |
| One credential for the domain, the hosting and the WordPress install | Hostinger | Registers, writes DNS, provisions hosting and deploys. Install a scoped entry point unless you need all 396 tools. |
The website-building MCPs worth installing
Ordered by how much of the job each one can actually do. Tool counts are what the server reported when we ran it, not what its README claims.
WordPress
10 min setupIt is the one entry in this category that edits a site most of the web already runs, and it does it without a page builder or a proprietary API — an application password and the REST API that ships with WordPress 5.6 and later. The multi-site design (`list_sites` first, then a `site` argument on everything) also makes it usable for an agency managing a fleet.
npx -y @cavort-it-systems/wordpress-mcp
Webflow
10 min setupMost CMS MCPs stop at the content record. Webflow's reaches the design surface, so "add a hero section with a CTA to the home page" is a tool call rather than a set of instructions for a human. The OAuth flow also means no long-lived site token sitting in a config file.
Remote MCP — add https://mcp.webflow.com/sse as a connector and authorize via OAuth
Contentful
10 min setupAgents are good at producing content and bad at guessing schemas. This server hands them both: `get_initial_context` is a documented mandatory first call that loads the space's shape, `get_content_type` returns the field contract, and `get_entry_snapshot` gives a rollback path when a bulk edit goes wrong.
npx -y @contentful/mcp-server
Sanity
5 min setupSanity models content as queryable structured documents rather than fixed page records, which is the shape an agent handles best — it can ask "every post referencing this author" as a query instead of paging a list. The remote-plus-OAuth setup also removes the long-lived project token that every local CMS MCP asks you to paste.
claude mcp add Sanity -t http https://mcp.sanity.io --scope user
Ghost
10 min setupMost CMS servers hand an agent a publish tool and trust the prompt. This one makes the workflow structural: preview, hash, confirm, apply, then check the live page. The `audit_content` and `check_site_health` tools cover the other half — missing alt text, broken canonicals, unparseable cards — so an agent can find the problems as well as write the posts.
npx -y ghost-publisher-mcp@latest
Strapi
10 min setupStrapi is the CMS in this category that runs on your own server, which makes it the one an agent can be given a real staging copy of. And because the schema tools are exposed, an agent can scaffold a content type and immediately populate it — the two halves usually split across a developer and an editor.
npx -y strapi-mcp@latest
Hostinger
10 min setupMost of this category is single-purpose: a registrar MCP or a hosting MCP. Hostinger is both, plus the site builder, so an agent can run the entire "from nothing to a live site" chain without switching credentials. The v2 redesign also fixed the one thing that made it hard to use: 396 tool definitions no longer land in the context window — three do, and the agent searches for the rest.
npx -y hostinger-api-mcp@latest
Wix
< 1 min setupSite builders have been chasing "describe and ship" for a decade. The ChatGPT app delivers the cleanest version yet — the LLM drafts the structure and copy, Wix handles the layout system and hosting.
ChatGPT App: https://chatgpt.com/apps/wix
The full chain needs three MCPs, or one
Quick comparison
| MCP | Shape | Tools (verified) | Maintained by |
|---|---|---|---|
| WordPress | Page-owning builder | 200 | Community |
| Webflow | Builder + Designer canvas | Not probed (OAuth-gated) | Webflow |
| Contentful | Headless CMS | 73 | Contentful |
| Sanity | Headless CMS | Not probed (OAuth-gated) | Sanity |
| Ghost | Publishing, confirm-first | 24 | Community |
| Strapi | Self-hosted headless CMS | 20 | Community |
| Hostinger | Hosting + builder + domains | 3 (403 operations) | Hostinger |
| Wix | Prompt-to-site generation | ChatGPT App | Wix |
"Not probed" means the server is remote and OAuth-gated, so it cannot be run without an account on that platform. This directory lists tool names only when it has run the server and read them back — an absent count means not yet verified, never no tools.
Common gotchas
A publish tool is a deploy, on a builder
On WordPress, Webflow, Wix and Hostinger the platform renders the page, so an agent that publishes has already changed what visitors see. There is no preview-then-promote split the way there is on a hosting platform. Give the agent draft-only capability first and add publish once you have watched one full cycle.
Deleting a content type is not like deleting an entry
On a headless CMS the model is the schema. Contentful marks delete_content_type_field as irreversible once published, and Strapi’s delete_content_type drops the type along with every entry modelled on it, with no confirmation step. Entries are recoverable; models generally are not.
An application password inherits the whole user
WordPress application passwords carry every capability the user has. Handing an agent an administrator’s password means it can activate themes, delete users and install plugins. Create a dedicated user with the narrowest role that still does the job, and revoke the password when the work is done.
Schema tools often need admin credentials, not a token
Strapi is the clearest case: the API-token fallback cannot reach the schema endpoints, so the content-type tools silently stop working rather than returning a permission error. Getting them back means putting an admin email and password in an MCP config. Decide whether you want that before you start.
Page-builder layouts are opaque to a CMS MCP
Elementor, Divi and similar builders store layout in formats the WordPress REST API treats as a blob. An agent can change the post record and will report success, while the page a visitor sees does not move. If your site is built in a page builder, the MCP is for content around the layout, not the layout.
Frequently asked questions
What is the best MCP server for building a website?
It depends on who renders the page, and that is the only question that matters first. If the site already exists on WordPress, the community REST-API server is the most complete option — 200 verified tools for posts, pages, media, plugins and themes. On Webflow, the official remote MCP adds Designer canvas edits on top of the CMS. If the site does not exist yet, the Wix ChatGPT App is the one thing here that generates a working site from a one-line brief. If your own front end renders the pages, pick a headless CMS instead: Contentful or Sanity.
Can an AI agent build a whole website from scratch?
Partly, and it matters which part. Wix genuinely generates a site — pages, copy, layout — from a brief. Everything else in this category edits a site that already exists: Webflow can add a section, Contentful and Strapi can scaffold a content type, WordPress can create pages, Ghost can draft and schedule a series. The realistic pattern is generate or scaffold once, then hand the agent the maintenance.
What is the difference between a site builder MCP and a headless CMS MCP?
What happens when the agent publishes. On a builder — WordPress, Webflow, Wix, Hostinger — the platform renders the page, so publishing changes what visitors see immediately. On a headless CMS — Contentful, Sanity, Strapi — the agent changes content that a separate front end renders, so publishing is a content event and a deploy is still its own step. That is why headless setups pair naturally with a hosting MCP and builders usually do not need one.
Do the Wix and Shopify MCP servers actually edit my site?
No, and this catches people out. The @wix/mcp npm package exposes 12 tools, every one a search over Wix documentation — REST, SDK, Velo, CLI, Headless, Design System. Shopify’s official @shopify/dev-mcp exposes six, all documentation search and code validation. Both are genuinely useful when an agent is writing code for those platforms, and neither reads or changes a live site. Wix’s site generation runs through its ChatGPT App instead.
Which of these are official vendor servers?
Webflow, Contentful, Sanity and Hostinger publish their own. Wix publishes the ChatGPT App plus the separate developer-docs MCP. WordPress, Ghost and Strapi have no first-party server, so those entries are community wrappers around documented APIs. That is worth knowing before you hand one an administrator credential — Strapi’s schema tools in particular need an admin email and password, not a scoped token.
Is it safe to let an agent publish to a live site?
Only after one draft-to-publish cycle you have watched end to end. The risks are specific: WordPress’s wp_activate_theme changes the whole site’s appearance with no preview, Webflow’s publish tool ships immediately, and Contentful’s delete_content_type_field is irreversible once published. Give the agent the narrowest role that still works — on WordPress that means a dedicated user, not an administrator — and start on staging.
Which builder MCP has the strongest safety model?
Ghost, by a clear margin. Every tool that changes the site requires user_confirmed=true, and apply_change_set additionally demands the exact hash returned by a prior preview_changes against the same site — so an agent cannot approve its own change set from nothing. Image uploads read only from configured local roots and reject remote URLs, SVG and symlink escapes. It is community-built, which makes the care taken more notable, not less.
Can an agent manage several sites at once?
On WordPress, yes and by design: list_sites comes first and every other tool takes a site argument, which is what makes it workable for an agency fleet. Contentful scopes by space and environment, Sanity by project and dataset, and Webflow authorizes per site during OAuth. Hostinger reaches every website on the account behind the token, which is convenient and worth scoping deliberately.
More for building websites
See the full Website Builders category for every ranked MCP, or pair a builder with the domains and hosting categories for the whole register → build → deploy chain.
Related guides
Tutorial
How to Publish an AI-Built Website With an MCP (No Git, No Terminal)
7 min read
Ranked Guide
Best MCP Servers for Deploying Websites in 2026 (Ranked)
13 min read
Tutorial
How to Connect a Custom Domain to Your Site With an AI Agent (MCP Workflow)
7 min read
Setup Guide
Best MCP Servers for Domains in 2026 (Registrars + DNS)
10 min read
Setup Guide
Best MCP Servers for Design-to-Code in 2026 (Figma → React)
9 min read
Tutorial
How to Deploy a Website With an AI Agent (MCP Workflow)
8 min read