How to action Bricks client feedback with AI and MCP

A client pins “change this heading” on a Bricks page. Instead of copying the comment into an AI chat and explaining where it belongs, connect Reviso through MCP so your assistant can read the feedback and inspect the target. This guide shows a controlled workflow for making one change and checking it before closing the comment.

Current scope: Reviso’s direct Bricks editing tools are in Beta and require Pro on the site being edited. You bring your own compatible AI assistant. The steps below use the Cloud MCP route; Local access is a separate option for Agency users.

1. Prepare a small review on your site

Start with a staging copy and a current backup. Create a review for a Bricks page and leave one specific comment on the element you want changed. Include the desired wording or result, not just “fix this”. Check that the pin points to the intended element.

For example: “Replace this heading with ‘Websites your team can update’ and keep its current font size.” A bounded request is easier to inspect and verify than a request to redesign the whole section.

2. Connect your assistant to Reviso

Connect the WordPress site to Reviso Cloud and follow the Cloud AI assistant setup guide. Use the connection details shown in your Cloud dashboard’s Connect panel. For the Cloud route, the MCP server is https://getreviso.io/mcp.

Claude, ChatGPT and other MCP-capable clients can expose different connection options depending on their plan and configuration. Confirm that your client actually lists the Reviso tools before proceeding. A successful connection does not by itself confirm that the site supports builder edits.

3. Ask it to inspect before editing

Give your assistant the site, review and comment you want it to use. A useful first prompt is:

Read this Reviso comment and inspect the page and target element. Tell me what the client wants, whether your available tools support the change, and exactly what you would edit. Do not change the page or resolve the comment yet. If the target is ambiguous, ask me.

Check its proposed target against the pinned element. If the assistant cannot identify it reliably, clarify the request before it writes anything. Feedback access and builder editing are separate capabilities.

4. Apply one focused change

Once the proposal is correct, authorise that change. For example:

Apply only the heading text change we agreed. Preserve the existing styling and layout. Do not change shared styles, templates or unrelated elements. Report the tool result and snapshot reference, and leave the feedback open until I have checked the saved page.

Reviso’s supported editing tools create snapshots. Keep the returned reference with the work so you can identify the edit if you need to revert it. A revert may refuse to overwrite a page that has subsequently changed; investigate that conflict rather than forcing it blindly.

5. Check the saved page, then resolve the feedback

• Reload the page from the site, not just the assistant’s description of its work.
• Confirm the exact heading text and the correct element.
• Check desktop and mobile layouts, especially line wrapping.
• Check nearby links and buttons if the edit could affect them.
• Resolve the comment only after the result matches the request.

If your assistant has browser access, ask it to perform those checks and provide evidence. If it does not, check the page yourself. An edit tool reporting success confirms a write, not that the page looks right.

What if the tools are missing?

Check that the intended site is connected, the assistant has the expected access, and Pro is active for direct Bricks editing. Ask the assistant to list its available Reviso tools. If feedback tools work but editing tools do not, do not treat that as proof of a successful edit. Use the setup and troubleshooting guide to check the connection.

Can I use this with Etch, Elementor or Breakdance?

This tutorial covers Reviso’s direct Bricks editing workflow. A builder’s commenting support, its own MCP server and Reviso’s editing adapter are different things. Other tools may let your assistant implement feedback in another builder, but that combination needs its own compatibility checks. We are not claiming equivalent native editing support here.

Try Reviso with your next feedback round

Start with pinned website feedback, explore how Reviso works with AI assistants, or compare the plans. The public demo lets you try collecting feedback; the connected AI workflow is set up separately on your own site.