Library mode or site mode

The BYQ MCP does two different jobs, and they behave differently. Knowing which one you want clears up the most common confusion.

Library mode: bring BYQ pieces into your own code project

Your AI tool searches the BYQ library of sections, gems, wireframes and design systems, and writes what it finds into a React and Tailwind project that you own. Your tool needs Pro or Ultra for this. It does not touch a BYQ site, and it does not make Webflow, Framer or Figma output.

Site mode: build a BYQ website from your AI tool

Your AI tool creates and edits a site inside the BYQ Website Builder, and you watch it live in the editor. It works on any plan, and it uses none of your BYQ AI tokens, because your own AI plan does the work. Publishing the site needs Pro or Ultra, or hosting for that site.

Which to use when

• You want sections, gems or a design system inside your own app or website code: library mode.
• You want BYQ to host and run a website you describe to your AI: site mode.
• You want to use the built-in assistant instead of your own tool: that is not the MCP at all, see Start here: which way to build.

It is one connection

You connect once and both modes are available. On the approval page, keep Build sites ticked if you want site mode. Setup for each tool is on Connecting your AI tool. The step by step guide for building a site is Build with your own AI tool.

What costs what

• Getting sections, gems, wireframes and design systems through your AI tool costs no BYQ AI tokens, and needs Pro or Ultra.
• Building a site costs no BYQ AI tokens, and works on any plan.
• In both cases your own AI plan does the work, so heavy use counts against that plan's limits, not BYQ's.