A1 Gallery

A1 is a hand-curated gallery of real website designs. This MCP server puts it inside your coding agent, so you can ask for a reference and get structured JSON back instead of pasting screenshots and describing what you want.

Every site is captured at full length, split into its interior pages and its individual sections, then measured. You get the type sizes, spacing, radius, container width and palette taken off the rendered page — not guessed from a picture.

In the gallery right now: 1,165 sites · 3,209 captured sections · 2,860 full-page captures · 571 fonts · 517 designers and studios.

Endpoint

Access is free with an A1 account — 50 tool calls a day. A1 Pro raises that to 2,000 a day with a higher per-minute allowance.

Install

Your client opens a browser to sign in the first time it connects. Per-client instructions with one-click install links are at a1.gallery/mcp.

Claude Code — plugin

The plugin in this repository bundles the server with three skills, three slash commands and a research sub-agent. It teaches the agent how to use the gallery, which the bare connector does not.

/plugin install a1-gallery --marketplace bryntay/a1-mcp

On Claude Code before 2.1.275, add the marketplace first:

claude plugin marketplace add bryntay/a1-mcpclaude plugin install a1-gallery

Then run /mcp and authenticate. See Plugin below for what it adds.

Claude Code — connector only

claude mcp add --transport http a1 --scope user https://www.a1.gallery/api/mcp

Then run /mcp and sign in when it prompts.

Codex CLI

codex mcp add a1 --url https://www.a1.gallery/api/mcp

Cursor and Claude Desktop

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

VS Code (1.99+ with GitHub Copilot)

{  "servers": {    "a1": {      "type": "http",      "url": "https://www.a1.gallery/api/mcp"    }  }}

Windsurf

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

Zed (0.168+)

{  "context_servers": {    "a1": {      "url": "https://www.a1.gallery/api/mcp"    }  }}

What you can ask for

• "Find three brutalist law firm sites and show me their heroes."
• "What type scale do agency heroes actually use?" — quartiles across every site, not one example.
• "Show me pricing pages that mention usage-based billing." — full-text search inside the page copy.
• "What do portfolio FAQs say about refunds?" — extracted Q&A pairs with frequencies.
• "Rebuild this pricing section." — palette, type, spacing and radius as measured values.

Tools

All 17 tools are read-only and annotated readOnlyHint: true.

Websites

Sections

Pages

Fonts and creators

Full descriptions, parameters and response shapes come back from tools/list.

Plugin

Installing the connector gives an agent 17 tools. It does not tell the agent that analyze_design_tokens answers "how big should this be" better than five screenshots, or that a lowSample flag means stop generalising. The plugin carries that.

Skills

Commands

Sub-agent

design-researcher handles open briefs that need several searches — an aggregate pass, a couple of targeted searches, then the values to build with. It returns a brief and never edits files.

Why aggregates use quartiles

analyze_design_tokens reports p25, median and p75 rather than an average. Design values are long-tailed — one site with a 180px hero heading drags the mean somewhere useless.

Narrow slices thin out fast. Ask for pricing sections on shops and you may be looking at a handful of examples. When that happens the response carries lowSample: true and reports raw counts instead of percentages, so the agent can say "here are four examples" rather than inventing a norm.

Notes

Site descriptions and section copy are third-party website content. The tool descriptions flag them as untrusted external data.

This repository holds the manifest and the docs. The server itself is closed-source and hosted at a1.gallery.

Support

Issues and questions: open an issue or email [email protected].