MCP

The MCP is a connection that lets your AI tools reach the BYQ library directly. Connect it once and tools like the Claude app, Claude Code, Cursor, Codex or Lovable can search BYQ and pull sections, gems and design systems straight into your project — no copy-pasting from the site. Full details are in the MCP documentation.

Supported out of the box: the Claude web and desktop app, Claude Code, Cursor, Codex and Lovable. Any other agent that can call a remote MCP server over HTTP will work too. Setup differs by tool: the Claude app connects over OAuth with no key at all, while the others use your BYQ address plus a generated key. Both routes are in Connecting your AI tool.

It depends on your tool. In the Claude web or desktop app there's no key and no snippet — BYQ Supply is listed in Claude's connector directory, so you find it, click connect, and sign in with your BYQ account. For Claude Code, Cursor, Codex and Lovable it's three steps: generate your MCP key, paste the snippet for your editor, restart the tool. Claude Code uses a single terminal command, Cursor a JSON config, Codex a TOML config, and Lovable two fields under Settings → MCP. The setup page gives you a ready-made snippet with your key already filled in. See Connecting your AI tool for all of them.

Generate it from your MCP setup page, and manage your keys anytime under Settings → Developers. The key is shown once, so store it like a password — once you refresh the page it's gone. You can always generate a new one, and the old one stops working.

Four things. It can search and pull sections — your AI finds one in the BYQ library and fetches a full integration prompt: a React and Tailwind reference build, the complete design spec, setup notes, and instructions to adapt it to your project. It can search and add gems, the small interaction effects like magnetic buttons, marquees and scroll reveals that you drop onto something already built. It can search and pull wireframes, unstyled layout structures. And it can search and apply design systems as DESIGN.md, tokens.json or CSS to style what it builds. You describe what you want in plain language and your AI handles the rest.

Yes. The MCP is a Pro and Ultra feature — the Free plan doesn't include MCP access. On Pro or Ultra you get full MCP access for Claude, Cursor, Lovable, and other supported AI tools, and your AI can pull anything your plan gives you access to.

Usually one of four things: you didn't restart the tool (most only load servers at startup), your key is mistyped or truncated (regenerate and re-paste), the server address is off (copy it exactly), or you're on the Free plan — the MCP needs Pro or Ultra. If you're using the Claude app there's no key involved, so check that the connector shows as connected and that you completed the sign-in. More checks are in Connecting your AI tool.

Not directly — the MCP is for building in code. What it returns is a React and Tailwind build plus a full design spec, so it lands in a codebase rather than in the Webflow Designer. If Webflow is your destination, pair it with the Converter: run the generated section through it and it becomes a native Webflow section with real elements and real classes. The MCP gets you polished, on-brand code fast; the Converter turns that code into native Webflow structure.

Yes. The BYQ MCP is just one of the tools your AI can connect to at once. Running it next to other MCPs — an image-generation one, for example — lets your AI pull an on-brand section from BYQ and create custom imagery to fill it in the same breath, so the sites you build feel genuinely bespoke.

It's in active development. It already reaches the whole library — sections, gems, wireframes and design systems — and works across the major AI tools, but you'll occasionally hit rough edges as we improve how it searches and formats results. If something doesn't work the way you'd expect, your feedback directly shapes what we fix next.