Thrive Architect MCP tools
Available in EMCP 3.17.0. Thrive Architect stores content as native HTML with its own element structure and styles. EMCP Pro reads that content and installed element definitions, then saves supported changes through Architect’s native pipeline. The result remains recognizable to the visual editor.
Requirements and setup
Section titled “Requirements and setup”- Check installed versions. Thrive Architect 11.0.x, tested on 11.0.0.1. EMCP Pro is required.
- Enable the integration. Open EMCP Tools > Page Builders and select this standalone builder. Gutenberg and enabled block packs remain available.
- Connect and inspect. Reconnect your MCP client, read context and schemas, and enable the write tools needed for the task. Start with a draft and inspect the native editor.
Native workflow
Section titled “Native workflow”Targeted operations add, replace, move or remove supported elements. Omitted CSS and settings are preserved, which matters when changing copy on an already styled page. Local content templates and symbols can be discovered without implying permission to modify shared assets.
Read native HTML and controls
Section titled “Read native HTML and controls”Inspect the page hash and controls for the intended element.
Prepare a focused edit
Section titled “Prepare a focused edit”Change supported content while preserving unrelated CSS and settings.
Check Architect and the frontend
Section titled “Check Architect and the frontend”Verify element recognition, responsive output, images and anchors.
Tool reference
Section titled “Tool reference”All names use the emcp-tools/ namespace. Read the live input schema for optional fields, enums, limits and confirmation requirements; this table lists required inputs only.
| Tool | Access | Purpose | Required inputs |
|---|---|---|---|
thrive-get-context | Read | Read version, target site and supported scope. | None |
thrive-list-elements | Read | Discover installed native element identifiers and availability. | None |
thrive-get-element-schema | Read | Read native controls and starter HTML for an installed element. | type |
thrive-list-pages | Read | List accessible pages and Architect state. | None |
thrive-get-page | Read | Read native HTML, page CSS, settings, element keys and content_hash. | post_id |
thrive-create-page | Write | Create a draft and initialize it through the native Architect save pipeline. | title |
thrive-set-page-content | Write | Save native HTML and optional CSS with a current hash; preserve omitted page settings. | post_id, expected_hash, html |
thrive-add-element | Write | Append native element HTML to a container key (or root). Read its native schema first. | post_id, expected_hash, parent_key, html |
thrive-replace-element | Write | Replace one keyed element with native HTML; retain needed classes, keys and descendants. | post_id, expected_hash, element_key, html |
thrive-move-element | Write | Append an existing element to a container; reject cycles. | post_id, expected_hash, element_key, parent_key |
thrive-remove-element | Write | Remove one keyed element and its descendants. | post_id, expected_hash, element_key |
thrive-list-library | Read | Discover accessible local content templates and symbols without changing shared content. | None |
Example request
Section titled “Example request”Build a Thrive Architect draft with a hero, service columns, images and a contact button. Use native elements and page-local responsive CSS; keep the existing theme header.
Read current state before editing and re-read after each save. If a hash is stale, inspect the changed document before rebuilding the request. A successful save is not proof of correct visual output: inspect the native editor and frontend.
Supported scope
Section titled “Supported scope”- Requires EMCP Pro, supported Architect and Thrive selected in Page Builders.
- Basic sections, columns, text, images, content boxes, buttons and dividers are authorable. Discovery does not imply every element is writable.
- Cloud landing templates, shared-symbol edits, forms/scripts, Thrive Theme Builder and Thrive Optimize are excluded.
Troubleshooting
Section titled “Troubleshooting”If tools are missing, check versions, dependencies, integration selection, tool switches and user capabilities. Reconnect long-lived MCP clients after plugin updates or selection changes. If output differs after saving, inspect the native document and styles before retrying; do not bypass the adapter with direct metadata writes.
See the Thrive Architect integration overview, builder setup guide and agent skills.