Set up A1 MCP in Figma
Add A1 as a custom connector and the Figma agent can pull real websites, sections, fonts and measured colour palettes straight into your file. Works in Figma Design and Figma Make on paid plans.
Set it up
Open your connectors
In a Figma Design or Figma Make file, open the agent chat. In the prompt box, click Add context, hover over Connectors, then click Manage.
Create a custom connector
Open the Created by you tab and click Create. Name it A1, paste this as the MCP server URL, then click Create.
https://www.a1.gallery/api/mcpConnect and sign in
Click Connect on the A1 connector, sign in with your A1 account and click Allow. Leave Advanced settings empty — Figma picks up A1’s sign-in on its own.
Done
What you can ask
Find dark agency hero sections on A1 and design one in this frame
Set up text styles from the type sizes A1 measured on landing page heroes
Find three minimal portfolio sites on A1 and turn their colours into a palette
17 tools cover whole websites, individual sections, full-page captures, fonts, measured colour palettes, and creators. See the full tool list.
Common questions
Model Context Protocol is an open standard that lets AI coding agents call external tools mid-task. Connect A1 once and your agent can look up real websites, fonts, and colour palettes as structured data — without you pasting screenshots or describing what you want.
Free with an A1 account. The first time you connect you’ll sign in — it’s free — and then you get 50 requests a day. A1 Pro raises that to 2,000 a day with a faster per-minute allowance.
Type @ in the agent chat — A1 shows in the list of connectors once it’s connected. If you can’t add connectors at all, an admin may have turned them off for your organisation.
Published website metadata: name, URL, fonts, colours, styles, technologies, and categories. Section screenshots for individual UI components — hero, pricing, features, CTA, footer, and more — each with the design values measured off the live page: palette as hex with roles, heading and body type, spacing, radius and layout, plus the copy read out as structured data, so a pricing section returns its tiers and their prices and an FAQ returns its questions and answers. Full-page captures of sub-pages — pricing, about, careers, docs, changelog and more — for seeing how a whole page is put together rather than one component. Creator profiles: designer and studio names, bios, and social links. No private or unpublished data is accessible.