Thrive Architect MCP integration
Thrive Architect MCP integration
Build native Thrive Architect landing pages with EMCP Pro. Inspect element controls, edit supported HTML and CSS, and discover local content templates.
Pro integrationThrive Architect 11.0.x, tested on 11.0.0.1
Thrive Architect workflow to review
| Step | Review point |
|---|---|
| Read native HTML and controls | Inspect the page hash and controls for the intended element. |
| Prepare a focused edit | Change supported content while preserving unrelated CSS and settings. |
| Check Architect and the frontend | Verify element recognition, responsive output, images and anchors. |
A practical place to start
Read native HTML and controls. Then build and review.
- 01
Read native HTML and controls
Inspect the page hash and controls for the intended element.
- 02
Prepare a focused edit
Change supported content while preserving unrelated CSS and settings.
- 03
Check Architect and the frontend
Verify element recognition, responsive output, images and anchors.
Built for Thrive Architect
Thrive Architect content your team can keep editing
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.
Work with the native design model
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.
Connect your AI to the right tools
Open EMCP Tools > Page Builders and select this standalone builder. Gutenberg and enabled block packs remain available. 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. Available in EMCP 3.17.0. Check compatibility before updating the vendor builder; an unsupported version can prevent its tools from appearing.
Read the Thrive Architect tool reference for operations and tested boundaries. The page-builder setup guide explains selection and Gutenberg coexistence.
Get connected
Put Thrive Architect in your AI’s toolkit.
- 1
Check installed versions
Thrive Architect 11.0.x, tested on 11.0.0.1. EMCP Pro is required.
- 2
Enable the integration
Open EMCP Tools > Page Builders and select this standalone builder. Gutenberg and enabled block packs remain available.
- 3
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.
Then connect Claude Code, Claude Desktop, or Cursor to use the Thrive Architect tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Thrive Architect, supported operations, and the workflow on your site.
Is Thrive Theme Builder included?
No. Architect is the page editor covered here. Theme Builder and Optimize are separate products.
Will text changes replace page CSS?
Omitted CSS and settings are preserved. Read the current page first and inspect the result after saving.
Can I browse cloud templates?
The integration discovers local content templates and symbols. Cloud downloads and shared-symbol editing are excluded.
Your tools. Your WordPress site.