Inspo vs Refero
Inspo and Refero both serve the design reference space, but with different primary users in mind. Inspo is an MIT-licensed MCP server built for AI coding agents; Refero is a paid design-inspiration product built for human designers.
| Feature | Inspo | Refero |
|---|
| License | MIT | Proprietary (paid) |
| Price | Free | Paid subscription |
| Primary user | AI coding agent | Human designer |
| Archive | 832 sites, 2,320 pages with DESIGN.md | Curated screenshots |
| Interface | MCP tools (agent-queryable) | Visual gallery browser |
| Self-hosting | Yes (clone + pnpm) | No |
| API access | MCP server, 15 tools | No public API |
Inspo is the stronger choice when the consumer of the reference material is an AI assistant. Its 15 MCP tools, semantic search, and per-site DESIGN.md files are structured for machine use: an agent can call recommend(brief) and get actionable design context it can apply directly without a human interpreting a screenshot first.
Refero is worth considering when the workflow centers on human designers browsing visually, building client mood boards, or presenting design directions for review. Its paid offering focuses on that gallery experience, which Inspo does not try to replicate.
The use cases are distinct enough that teams using both are not doubling up. Inspo serves the agent before it writes code; Refero serves the designer before they brief the agent or review the output.