The BYQ MCP lets your AI tool do two jobs. Library mode: your AI tool searches BYQ sections, gems, wireframes and design systems and writes them into your React and Tailwind project. Site mode: your AI builds and edits your own BYQ website, on your own AI plan, with no BYQ AI tokens. Neither mode produces Webflow, Framer or Figma output.
The MCP exists because the fastest way to use BYQ inside an AI workflow is to let the AI reach the library itself. Normally you browse the site, find a section, copy its prompt or code, and paste it into your tool by hand. The MCP removes that round-trip: it gives Claude, Claude Code, Cursor, Codex, Lovable and other AI tools a direct line into BYQ, so they can find the right piece and add it for you, without you leaving your editor.

MCP stands for Model Context Protocol — an open standard for connecting AI tools to outside services. In plain terms: you connect the BYQ MCP once, and from then on your AI tool can reach into the library on its own. In library mode it gains four abilities. In site mode it can also build your BYQ sites. The four library abilities:
You describe what you want in plain language, your AI does the searching and fetching, and the result lands in your project.
AI tools are fast at generating layouts but generic by default — the same spacing, the same shadows, the same rounded buttons everyone else gets. The MCP gives your AI access to production-grade building blocks and the visual language of polished BYQ templates, so what it produces starts from a real design foundation instead of a blank slate. You stay in the tool you already work in; BYQ becomes something your AI can reach into on demand.
In library mode, what lands in your project is React with Tailwind, adapted to your conventions. It is code for your own project, not a design file. In site mode your AI edits your BYQ site directly, and you watch every change in the BYQ editor.
If you want library output in Webflow, the Converter can help, but it cannot read React. Ask your AI to give you the rendered result as plain HTML and CSS first. For many Webflow projects, copying a Section straight from the library is simpler.
Supported out of the box: Claude (web and desktop app), Claude Code, Cursor, Codex and Lovable. Any other AI tool that lets you add an MCP server by web address works too.
Setup differs by tool. The Claude app, Codex, Claude Code and Cursor can sign in with your BYQ account, with no key to handle at all (in Claude, pick BYQ Supply from the connector directory). Lovable and other tools use your BYQ address plus a generated key. Both routes are covered in Connecting your AI tool.
Any valid key connects on any plan. Library mode (finding and pulling sections, gems, wireframes and design systems) needs Pro or Ultra; on Free you get a prompt to upgrade. It uses no BYQ AI tokens and doesn't count toward your 300 section copies. Site mode works on every plan, and publishing a site needs Pro, Ultra or hosting for that site.
If something doesn't work the way you'd expect, tell us. Your feedback shapes what we fix next.
The MCP links the library to your AI workflow. It pulls from the same Sections and Design Systems you can browse on the site, and, through plain HTML, it can feed the Converter when your destination is Webflow. We cover the broader picture in Build with AI.