Curio — Design Style Library
Let agents search Curio’s style library and pull ready-to-apply design specs while building UI in the agent.
Overview
Curio MCP is a MCP server for the Build phase that lets AI agents search design styles and fetch ready-to-apply design specs from Design by Curio.
What is this MCP server?
- Remote MCP at mcp.designbycurio.com (streamable HTTP, v0.2.0)
- Search real design styles and fetch apply-ready design specs
- No auth in published server.json—public style library endpoint
- Website and docs at designbycurio.com/mcp
- Server version 0.2.0
- Single public streamable-http remote
- Documented at designbycurio.com/mcp
What problem does it solve?
Agents default to generic “AI slop” UI because they have no structured access to real design styles or specs.
Who is it for?
Solo founders shipping landing pages or app UI who want agent-driven implementation with a consistent, library-backed visual direction.
Skip if: Teams needing full design-system governance, Figma sync, or backend-only workflows with no UI work.
What do I get? / Deliverables
After registering the Curio remote, your agent can pull named styles and concrete specs you can implement in frontend code in the same session.
- Retrieved design style matches from Curio search
- Ready-to-apply design specification for agent implementation
- More consistent UI direction across agent-generated screens
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the server exists to apply visual design decisions during product UI implementation. Frontend subphase covers choosing and implementing look-and-feel; Curio supplies named styles and specs agents can follow in code.
How it compares
Hosted design-style library MCP, not a local Tailwind or shadcn install skill.
Common Questions / FAQ
Who is com.designbycurio/curio for?
Builders and agents implementing frontend UI who want searchable, spec-backed design styles instead of one-off aesthetic prompts.
When should I use com.designbycurio/curio?
Use it during Build when you are defining or implementing screens and need a concrete style reference the agent can apply in code.
How do I add com.designbycurio/curio to my agent?
Add the streamable HTTP remote https://mcp.designbycurio.com/mcp in your MCP client configuration; no API key is listed in the published manifest.