Three ways to use Brixies MCP
Once your assistant is connected to Brixies, you can choose how the layouts reach your site.
All three workflows use the Brixies library. The difference is how you receive, customize and import the layouts.
| Workflow | How layouts reach your site | What you need |
|---|---|---|
| Generate a copy link | Open the link, copy the layouts and paste them into Bricks. | Brixies MCP and access to your Bricks editor. |
| Get JSON in chat | Receive the layout JSON in the conversation and copy it into Bricks. | Brixies MCP and access to your Bricks editor. |
| Import directly into Bricks | Your assistant imports the layouts through the Bricks Builder MCP. | Brixies MCP and a separate Bricks Builder MCP connection to your destination site. |
Your assistant may ask you to confirm class names before preparing the layouts. See the BEM class names guide for details.
Generate a copy link
This is the recommended starting point.
Describe the page or layouts you need. Your assistant searches Brixies, helps you choose the layouts and returns a link where you can copy the prepared content.
- Describe the page and sections you need.
- Review the proposed layouts.
- Ask your assistant to generate a copy link.
- Open the link and sign in to the Brixies account that owns it.
- Copy the layouts and paste them into your Bricks editor.
The full layout JSON stays out of the conversation, which generally reduces AI token usage.
When to choose this workflow
- You want a straightforward way to use layouts.
- You prefer to review and paste the result yourself.
- You want to keep AI token usage lower.
- You do not have the Bricks Builder MCP connected to your site.
Example prompt
Find Brixies layouts for a dental clinic landing page using my framework preference. Include a hero, services, testimonials and a contact section. Show me your proposed selection before generating a copy link.
Get JSON in chat
Choose this workflow when you want your assistant to work with the layout JSON directly.
You can ask it to adapt text or make specific changes before delivering the final JSON.
- Describe the layouts you need.
- Tell your assistant that you want the result as JSON in the chat.
- Explain any changes you want.
- Review the result and copy it into Bricks.
- Check the imported page in the editor and on the frontend.
The layout JSON becomes part of the conversation. Large layouts and repeated revisions can use more AI tokens.
When to choose this workflow
- You want to review the layout data.
- You want the assistant to adapt content before you import it.
- You are comfortable working with JSON.
- You want to handle the final import yourself.
Example prompt
Find a Brixies hero and services section using my framework preference. Show me your proposed selection first. After I approve it, adapt the text for a dental clinic and deliver the Bricks-compatible JSON in this chat. Do not generate a copy link or import anything into my site.
Review customizations before publishing. Ask for specific changes and check that the imported layouts still look and work as expected.
Import directly into Bricks
Choose this workflow when you want your assistant to place the layouts into your site through the Bricks Builder MCP.
Brixies supplies the layouts. The separate Bricks Builder MCP connection provides access to the destination site.
- Connect your assistant to Brixies MCP.
- Connect it to the Bricks Builder MCP on your destination site.
- Identify the exact site and page you want to edit.
- Describe the layouts and changes you need.
- Review the proposed import and confirm whether to add to or replace existing content.
- Check the imported result in Bricks and on the frontend.
To connect your destination site, follow the official Bricks Builder MCP setup guide.
When to choose this workflow
- You already have the Bricks Builder MCP connected.
- You want your assistant to handle the import.
- You want to continue editing the destination page with your assistant.
- You can review the changes on the destination site.
Layouts with custom code
Some layouts include custom code that needs special handling during direct import.
Our direct-import workflow disables PHP execution in Code elements. Depending on the layout, CSS can be kept in its original location or moved to the section’s global class. HTML and JavaScript may also need review.
Read the direct-import guide before using this workflow with layouts that contain custom code.
Example prompt
Use Brixies MCP to find a hero and services section using my framework preference. I want to import them through the Bricks Builder MCP. Before making changes, confirm the destination site, the page, the selected layouts and whether existing content will be preserved. Explain any custom-code handling the layouts require.
Compare AI token usage
AI token usage depends on how much information your assistant reads and writes, the size of the layouts and the number of revisions.
| Workflow | What affects token usage |
|---|---|
| Copy link | The full layout JSON stays out of the conversation. This generally uses fewer tokens. |
| JSON in chat | The assistant receives and returns layout JSON. Larger layouts and revisions increase usage. |
| Direct import | The assistant may read layout JSON, inspect the destination site, send import data and verify the result. Usage depends on the steps needed. |
Direct import is not always more expensive than receiving JSON in chat. The amount of data and the number of tool calls matter more than the workflow name alone.
AI token usage and Brixies usage limits are separate. A workflow that uses fewer AI tokens still follows your Brixies limits.
Tell your assistant which workflow you want
Include your preferred delivery method in your request:
- “Generate a copy link.”
- “Deliver the JSON in this chat.”
- “Import through the Bricks Builder MCP after I confirm the destination.”
You can choose a different workflow for another task without changing your Brixies API key.
If you are unsure, start with a copy link. It lets you review and import the layouts yourself with less setup.