> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wpbevel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bevel MCP

> Connect Claude, ChatGPT or any MCP client to your site and let it build with Elementor and Bevel Kit. Everything runs on your site.

Bevel MCP turns a WordPress site into an **MCP server**: an endpoint an AI assistant connects to, with a set of tools it may use. Claude, ChatGPT, Claude Code, Cursor and any other Model Context Protocol client can then read the site and build in it: the design system, pages, templates, menus, media, fonts and SEO, all through Elementor and Bevel Kit's widgets.

## What makes it different

Connecting an assistant to WordPress is easy. Getting a site worth keeping out of it is not. An assistant left to write Elementor JSON produces pages that import and look wrong: buttons without hover states, cards with no padding, photos cropped through faces, three identical grids in a row.

Bevel MCP carries the house rules. A **rule engine** reads every element tree before it is saved, repairs what it can (mobile twins, hover colours, line-heights, padding, image crops, logo variants) and refuses what it cannot, with a reason the assistant can act on. It also holds every page to one of twenty **looks**, so a site built over a week still looks like one site.

## The building runs on your site

There is no build service. The rule engine, the page generator, the build guides, the icon maps and the tool catalogue are files inside the plugin. The only intelligence off-site is the assistant, which is yours.

## AI generations

Creating pages and blog posts draws on the daily **AI generations** of a Bevel plan, including the free one. One generation is one page (`create_page`, `build_page`) or one blog post (`create_post`). Headers, footers, logos, edits, menus, media, SEO and the design system are not counted and work without an account.

| Plan    | AI generations a day | Websites |
| ------- | -------------------- | -------- |
| Free    | 5                    | 1        |
| Starter | 20                   | 1        |
| Pro     | 50                   | 10       |
| Agency  | Unlimited            | 1,000    |

The count is kept by my.wpbevel.com per license and per UTC day, and shared by every site on the license. The site connects once, under **Bevel → Site Settings → Account**; **Bevel → MCP Connectors** shows today's count and when it resets. A generation is drawn only after something was made, so a page the rule engine refuses costs nothing, and each generating tool's response tells the assistant how many are left. Current plans and prices: [my.wpbevel.com/pricing](https://my.wpbevel.com/pricing).

Bevel MCP is downloaded from your license page at [my.wpbevel.com](https://my.wpbevel.com) rather than WordPress.org, and updates through **Plugins → Updates** while the site is connected.

## What leaves the site

The account server is told which tool drew a generation, the site's address and its license, never what was built. Beyond that the plugin contacts three things, each only when asked: the openly-licensed photo library at api.openverse.org when the assistant searches for a picture, the website you name to `fetch_brand`, and a Google Drive or Dropbox link you paste. See [Security and privacy](/mcp/security).

## What the assistant can do

| Area          | Tools                                                                                                                                               |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Design system | read and set global colours, typography, buttons, the body background and the site's look; install the brand's own fonts                            |
| Pages         | create pages from an element tree, edit them band by band, read an outline                                                                          |
| Templates     | headers, footers, single-post, archive, 404, popups, mega menus, loop cards, WooCommerce product and archive templates                              |
| Content       | blog posts, navigation menus, media with alt text, meta descriptions                                                                                |
| Assets        | your brand assets dropped in before the chat, a business's existing logo and colours from its website, openly-licensed photos, a generated wordmark |
| Maintenance   | cache clearing, WebP conversion, database cleanup, a read of form submissions                                                                       |

Every area is a **capability** you switch on, per site and per connection. See [Capabilities and scopes](/mcp/capabilities).

## What it needs

* WordPress 6.8 or newer, PHP 8.0 or newer.
* Elementor 3.25 or newer.
* **Bevel Kit**. The widgets, theme builder and site settings the assistant builds with live there. Without it the endpoint stays closed rather than building pages full of widgets the site cannot render.
* A site the assistant can reach. claude.ai and ChatGPT connect from their cloud, so a site on your own machine works with desktop clients only. See [Connecting](/mcp/connect).

## Where to go next

1. [Connecting an assistant](/mcp/connect)
2. [Your first build](/mcp/building)
3. [Brand assets](/mcp/brand-assets), so the assistant never asks for a file
4. [The tools](/mcp/tools), if you want to know exactly what it can call