Skip to main content

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.

FAQ​

When should I use this MCP Assist page?

Use this page when you need to understand the workflow, settings, or decisions related to MCP Assist. It is most helpful before editing a live asset, publishing changes, or troubleshooting behavior in an Atomicat workspace.

What should I check before changing MCP Assist?

Confirm that you are in the correct workspace, project, page, funnel, site, or account area. Review access permissions, saved changes, publishing status, and any connected integrations before making updates.

How do I verify that MCP Assist is working correctly?

Preview the affected page or feature, test the main user path in a fresh browser session, and confirm that forms, redirects, tracking, products, quizzes, or publishing states behave as expected.

What should I do if MCP Assist does not work as expected?

Recheck the configuration described on this page, save the changes again, clear browser cache if needed, and test with a simple version of the setup. If the issue continues, collect the page URL, workspace details, and screenshots before contacting support.