Set up A1 MCP in Windsurf

A short config connects Windsurf to a hand-picked gallery of real websites — sections, fonts, and measured colour palettes as structured data.

Set it up

Add the config

Add this to ~/.codeium/windsurf/mcp_config.json.

{
  "mcpServers": {
    "a1": {
      "serverUrl": "https://www.a1.gallery/api/mcp"
    }
  }
}

Restart Windsurf
Done

What you can ask

Find minimal SaaS landing pages built with Framer

What fonts are most popular across SaaS sites?

Find sites with a similar feel to Stripe

Who designed the Firecrawl site and what else have they made?

Find dark, expressive portfolio sites

What’s been added to A1 recently?

17 tools cover whole websites, individual sections, full-page captures, fonts, measured colour palettes, and creators. See the full tool list.

Use a different tool?

A1 MCP also works in Claude Code, Claude, Cursor, Codex, VS Code and Zed. Anything else that speaks MCP can use the server URL directly — see the MCP page.

Common questions

What is MCP?

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.

Does this cost anything?

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.

How do I verify it’s connected in Windsurf?

Open Settings, then Cascade, then MCP servers — or the MCPs icon in the Cascade panel. a1 shows there once the config is saved and Windsurf has restarted.

What data does it return?

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.