SectionMate MCP

SectionMate MCP connects your AI assistant to WordPress so it can build and edit page sections — a hero, a pricing table, an FAQ, a features row — directly in Elementor, Gutenberg or Spectra.

Build one section at a time. This is the most important thing to know. The AI can generate a whole page in one request, but the results are noticeably better when you do one section, look at it, adjust it, then move on. Each section gets the AI’s full attention instead of a fraction of it — and you catch a wrong direction after one band instead of after twelve.

Nothing is saved until you approve it. Every edit shows you a preview and waits for your confirmation.

Install and connect

1. Install and activate the plugin.
2. Open SectionMate MCP in the WordPress admin menu.
3. Type a name for the AI app you are connecting — “Claude”, “Grok”, “Cursor” — and click Create connector URL.
4. Copy the URL. It is shown only once. It already contains your sign-in details, so there is nothing else to fill in.
5. In your AI app, add it as a remote MCP server (some apps call this a “connector” or “custom connector”).
6. Ask for a section: “Add a pricing section to page 12 with three plans.”

Your site needs to be reachable over HTTPS. For a site on your own computer, use a tunnel such as Cloudflare Tunnel or ngrok.

Getting good results

• One section at a time. Finish and review the hero before asking for the features row.
• Give it something to work from. A screenshot of a design you like, your brand colours, a logo, images already in your Media Library.
• Say what is wrong. “Make the cards taller”, “use the brand green” — it can read the page back and change specific blocks rather than rebuilding everything.
• Point at things visually. Logged-in editors get an Inspect overlay on the front end: click any block to grab a reference for the AI, or leave a note it reads on the next turn.
• You can edit anything by hand afterwards. It is ordinary WordPress content.

What it does not do

It builds content on a page. It does not set up your theme, your site-wide header and footer, or your menus. It can build a header-looking band as part of a page, which is not the same thing as a theme header.

Works with

• WordPress block editor (Gutenberg) — works out of the box
• Elementor (free)
• Spectra / Ultimate Addons for Gutenberg
• Spectra Blocks (V3)

Use one builder per page. Sections, headings, text, images, buttons and icons work on all of them; counters, countdowns, FAQ accordions, icon lists and galleries work wherever the builder provides them.

Not affiliated with or endorsed by Elementor, Brainstorm Force (Spectra), or Automattic.

Safety

The connector signs in as you. It can do exactly what your account can do and no more, every edit is recorded as yours, and you can revoke one connected app on its own without changing your password.

• Turn the MCP connector switch off when you finish. The plugin stays installed and your pages keep working.
• Prefer a local or staging site for big redesigns. On a live site, work on drafts and keep sessions short.
• Treat the connector URL like a password, because it contains one.
• If you deactivate the plugin, everything it built stays on your pages.
• Advanced: a code block can carry custom CSS and JavaScript. Writing JavaScript follows WordPress’s own rule and needs the unfiltered_html capability — administrators and editors have it on a normal single site.

Privacy

The plugin does not phone home, and it collects no analytics or telemetry of any kind. It adds no third-party scripts and no trackers to your pages.

It does use two external services, and one of them (Google Fonts) is requested by your visitors’ browsers. Both are described in External services below. Read that section before using the plugin on a site with GDPR or similar obligations.

External services

This plugin relies on the following external services. Each is listed with what it does, what is sent, when, and links to that provider’s terms and privacy policy.

Google Fonts (fonts.googleapis.com, fonts.gstatic.com)

What it is used for. When a page you compiled specifies a Google font family, the plugin enqueues that family’s stylesheet so the page renders in the font you chose. The plugin’s own admin screen and the logged-in front-end Inspect overlay also load one font (IBM Plex Mono) for their interface.

What is sent and when. The plugin builds a stylesheet URL containing only the font family names and weights the page asks for. Your visitor’s browser then requests that stylesheet from fonts.googleapis.com and the font files from fonts.gstatic.com. Those requests are made by the browser, so Google receives the visitor’s IP address and user-agent, as it does for any site using Google Fonts. This happens on the front end for pages that use a Google font, and in the admin/editor for the interface font. No personal data is sent by the plugin itself, and nothing is sent when a page uses no Google font.

Avoiding it. Pages that use only system or theme fonts make no request. If you need zero third-party font requests, do not specify Google font families when designing, and use a font-hosting plugin for the interface font.

Service provided by Google: terms of service, privacy policy, Google Fonts privacy FAQ.

Wikimedia Commons API (commons.wikimedia.org)

What it is used for. The optional search_placeholder_images MCP tool searches Wikimedia Commons for openly licensed photographs, so an AI agent can suggest real images for a design instead of inventing image paths that render blank. It is read-only and returns image URLs, dimensions, suggested alt text, and licence/attribution information.

What is sent and when. Only when you or your connected AI agent explicitly calls that tool. The request is made from your server and contains the search terms supplied in the call, plus a requested image width and result limit. No personal data, no site information, and no account or API key are involved.

Avoiding it. The tool only runs on request. If it is never called, the plugin never contacts Wikimedia. Turning the MCP connector off under Setup blocks it along with every other tool.

Service provided by the Wikimedia Foundation: terms of use, privacy policy, API documentation.

Images you choose to import (no fixed provider)

What it is used for. The import_media tool, and the media sideloading step of compile_and_insert / compile_elementor, download an image from a URL and add it to your Media Library so the page serves it locally rather than hotlinking.

What is sent and when. Your server makes an HTTP request to whatever URL you or your agent supplies — there is no fixed third party, and the plugin has no default host. It runs only on explicit request, requires the upload_files capability, and is confirm-gated: the first call returns a preview and nothing is downloaded until a second call confirms it. Whichever host the URL points at will see a request from your server’s IP address.

Avoiding it. Supply only URLs you trust, or upload images through the WordPress Media Library instead and reference them by attachment id.