Getting the most out of the MCP

A handful of habits make the MCP reliable, and a few honest limits are worth knowing about — the MCP is a fast bridge to the library, not a substitute for a final pass by you.

The MCP works best when you treat it as a fast, well-stocked assistant rather than a black box. These habits improve nearly every session, followed by the limits worth keeping in mind so the results don't surprise you.


Habits that get better results
  • Lead with the design system. Apply a style before pulling components, so everything generated afterward already matches. Re-skinning after the fact is always more work.
  • Name the section type explicitly. "Pricing," "hero," "footer" anchors a search far better than describing contents alone.
  • Review before you place. Glance at the matches your AI surfaces and steer it toward the right one before it fetches — it's quicker to redirect a search than to undo a placement.
  • Keep prompts conversational. You don't need to name tools or ids. Describe the outcome and let your AI sequence the searches and fetches.
  • Browse the site when you're unsure. The Sections library and Design Systems show everything the MCP can reach — find what you like visually, then ask for it by name.

What the MCP can't do

Being honest about the edges saves you time:

  • It reaches the library, not your whole project. The MCP searches and fetches BYQ content; it doesn't understand your existing codebase the way your AI tool does. Your AI handles the integration — the MCP just supplies the material.
  • Results follow your plan. Your AI can only fetch what your account has access to. Designated free sections and Design Systems work on Free; the rest follows your Pro or Ultra plan, exactly as on the site.
  • Components are a strong starting point, not a finished page. Like the rest of BYQ, the components are production-grade building blocks — you'll still adapt copy, imagery, and fit to your specific project.
  • It works one piece at a time. The MCP shines at pulling sections and systems individually and assembling from there, not at generating an entire multi-section site in a single call.

A note on beta

The MCP is in active development. The library it can search keeps growing, and how it formats and ranks results keeps improving. You'll occasionally hit a gap — a search that misses, a format that needs tidying — and when you do, your feedback directly shapes what we prioritize.

Where to go next

If you haven't connected yet, start with Getting Started. If Webflow is your destination, pair the MCP with the Converter. And for the full picture of how BYQ fits into an AI workflow, see Build with AI.