What is Brixies MCP?
Brixies MCP connects your AI assistant to the Brixies layout library.
MCP stands for Model Context Protocol. It lets a compatible assistant use tools to search Brixies, read your framework preferences and retrieve layouts for your project.
You describe what you want to build. Your assistant searches the library and helps you select and arrange existing Brixies layouts.
The result depends on the layouts available in the library and the instructions you provide.
Choose how to work
You can use Brixies MCP in three ways.
Recommended
Generate a copy link
Ask your assistant for a page or a selection of layouts. It returns a link where you can copy the prepared content and paste it into Bricks.
The full layout JSON stays out of the chat, which generally reduces AI token usage.
Your steps
- Describe the page or layouts you need.
- Open the link returned by your assistant.
- Sign in to the Brixies account that owns the link.
- Copy the layouts and paste them into Bricks.
Get JSON in the chat
Ask your assistant to deliver the layouts as JSON directly in the conversation.
You can request changes to the layout text before receiving the final JSON. Review the result before using it in Bricks.
This method generally uses more AI tokens because the layout JSON is received and returned in the conversation.
Import directly into Bricks
Connect your assistant to both Brixies MCP and the Bricks Builder MCP on your destination site.
Brixies supplies the layouts. The Bricks MCP provides the tools to import them into the site without manually copying and pasting.
Layouts containing custom code may need additional handling. The direct-import guide explains the options for keeping the original CSS or moving it to the section’s global class.
Identify the destination site and page, then authorize the import. Your assistant may need additional calls to inspect the site and verify the result.
Compare the workflows
| Workflow | How layouts reach your site | Connections needed |
|---|---|---|
| Copy link | You copy from the Brixies link and paste into Bricks. | Brixies MCP |
| JSON in chat | You copy the JSON delivered in the conversation and paste into Bricks. | Brixies MCP |
| Direct import | Your assistant imports through the Bricks MCP. | Brixies MCP and Bricks MCP |
Token usage varies with the size of the layouts, the changes requested and the number of tool calls. Direct import is not always more expensive than delivering the full JSON in the chat.
Use your preferred framework
Brixies can read the framework selected in your account preferences.
Available choices include AutomaticCSS, Core Framework, AT Framework, Vanilla and All frameworks. AutomaticCSS also has a version preference.
Choose your preference in Account -> Preferences. You can also explicitly request a different framework for a particular task.
Selecting All frameworks lets you explore multiple frameworks. It does not mean layouts from different frameworks can be combined into one prepared page.
Start with a clear request
Describe the type of page, the sections you need and their order.
Example prompt
Create a landing page for a dental clinic using my Brixies framework preference. Include a hero, services, testimonials, pricing and a contact section, in that order. Use the copy-link workflow and ask me before preparing the final link.
Your assistant may ask questions to clarify the selection or confirm class names before preparing the result.
Ready to connect?
Check the requirements, generate your API key and follow the connection guide for your assistant.