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 Code, Cursor, Lovable, and other AI agents a direct line into BYQ, so they can search for the right component or design system and apply it for you — without you leaving your editor.
[Image: a diagram showing an AI tool connected to the BYQ library through the MCP, with components and design systems flowing into a project]
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. It gains two 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.
The MCP works with any AI tool that supports remote MCP servers, including Claude Code, Cursor, Lovable, v0, and Bolt. Setup differs slightly per tool, but the idea is the same everywhere: connect once with a key, then mention BYQ in your prompts.
You generate an MCP key from your account, and the connection respects the same access as the rest of BYQ — the components and design systems your AI can pull are the ones your plan already gives you access to. Free designated sections and Design Systems stay available on Free; the rest follows your Pro or Ultra subscription, the same way it does when you browse the site directly.
The MCP is in active development. It already covers a wide slice of the library and works across the major AI tools, but you'll occasionally hit rough edges as we expand what it can search and how it formats results. We're improving it continuously, and if something doesn't work the way you'd expect, your feedback genuinely shapes what we fix next.
The MCP is the connective tissue between the rest of the library and your AI workflow. It pulls from the same Sections and Design Systems you can browse on the site, and it pairs naturally with the Converter when your destination is Webflow. We cover the broader picture in Build with AI.