MCP Assist
MCP Assist is available from the Page Builder header as an assistant entry point for page-level workflows.
The builder opens MCP Assist with page scope, which means the assistant context is tied to the current page rather than a specific selected element.
When to use MCP Assist​
Use MCP Assist when you need AI-assisted help while working on a page.
Possible use cases include:
- Reviewing page structure.
- Asking for page-level editing guidance.
- Planning copy or layout improvements.
- Working with builder-related workflows that support MCP context.
Scope​
The builder header opens MCP Assist at the page level.
Element-specific assistance may depend on the specific builder workflow and selected element support.
Best practices​
- Save important page edits before relying on any assistant-driven workflow.
- Review AI-assisted suggestions before applying them.
- Validate page behavior in preview after changes.
- Keep final responsibility for copy, compliance, tracking, and layout review with the editor.
Related docs​
FAQ​
What context does MCP Assist use from the builder?
MCP Assist opens from the Page Builder header with page-level context, so it is suited to reviewing or planning work for the current page rather than one isolated selected element.
Should I save before using MCP Assist?
Yes. Save important edits first so the assistant context and your current page state are easier to review.
Can MCP Assist replace manual QA?
No. Review AI-assisted suggestions and still test copy, layout, forms, buttons, tracking, SEO metadata, compliance, and mobile behavior before publishing.
Where should I learn more about MCP workflows?
Use the AtomicMCP docs for connection setup, tool categories, and example prompts that work across pages, sites, funnels, quizzes, leads, analytics, and videos.