Mcp

Google Design MCP

Remote MCP server at design.googleapis.com/mcp. Registry description: "Provides UX capabilities to enhance the design output and understanding of AI systems." Tool surface and auth flow not documented in any upstream README at ingest time.

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

When to use Google Design MCP

Choose if

You're exploring Google-hosted MCP endpoints and want to probe what design.googleapis.com/mcp exposes. The registry description suggests it targets UX/design assistance for AI systems, but the tool surface should be verified at initialize time before wiring into a production agent.

Avoid if

You need a documented, predictable MCP. This record has no upstream README — capability surface is unverified. Also avoid if you need design rendering, Figma manipulation, or non-Google design systems.

Risk Flags

MEDIUM scope No upstream README available at ingest time. Tool list, auth requirements, and exact capability surface are not documented in any public source the curator could fetch — agents should call initialize on design.googleapis.com/mcp to discover the actual tool set before relying on this in production.

Cost

Type: Unknown

Distribution

MCP Registry: com.googleapis.design/mcp

Use Google Design MCP from your agent

claude mcp add auxiliar -- npx auxiliar-mcp
# Then in your agent:
get_capability(id="com-googleapis-design-mcp")