Mcp

Google Design MCP

Official Google MCP for design assistance. Five tools observed at initialize: generate_color_scheme (palette from key colors), search_icons + icons_instructions (Material Symbols / icon library lookup), search_fonts + describe_font (Google Fonts catalog + character/weight metadata). Hosted at design.googleapis.com via Google's ESF.

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use Google Design MCP

Choose if

You're building a frontend-design or UI-generation agent that needs official Google Material/Fonts metadata in the loop — color palette generation, icon search, font lookup. Cleaner trust surface than scraping fonts.google.com, and the same auth substrate as other googleapis.com services.

Avoid if

You need design rendering, mockups, Figma manipulation, or non-Google design systems (Apple SF Symbols, FontAwesome, Lucide). Also avoid if you only need Google Fonts at static-asset time — the free CSS API at fonts.googleapis.com is simpler. This MCP is for in-loop design *decisions*, not asset delivery.

Risk Flags

  • LOW scope Five-tool surface scoped to color palettes, Google Fonts metadata, and Material icon search. Not a design-rendering or Figma-manipulation MCP — it answers reference / lookup questions only.
  • MEDIUM auth Hosted on a canonical googleapis.com origin (same trust surface as Google Cloud), but the registry entry doesn't document the auth flow. Confirm whether it requires GCP credentials before wiring into a production agent.

Cost

Type: Unknown

Distribution

MCP Registry
com.googleapis.design/mcp