Inspiration references should accelerate implementation, not create copying risk
Product teams collect screenshots and landing pages as visual references, then manually translate them into hierarchy, component plans, design tokens, and starter code. InspoMCP turns that process into a safe, inspectable developer workflow.
InspoMCP is an MCP server that accepts two or three UI reference screenshots and/or safe public URLs. It captures sanitized evidence, extracts page structure, runs local visual analysis, and synthesizes an original reusable UI kit. Developers can retrieve durable progress, generate an evidence-based kit, and request framework-specific starter code for one component card.
What it does
- Validates URLs to block localhost, private networks, unsafe redirects, and non-standard ports.
- Uses screenshots as primary evidence and safely captures public URL text for enrichment.
- Extracts sections, calls to action, cards, and hierarchy before visual synthesis.
- Persists runs, status, warnings, analyses, and generated kits in SQLite.
- Generates reusable component cards and starter code for Next.js/Tailwind, React/CSS, or framework-agnostic HTML/CSS.
- Adds privacy controls: secret rejection, text redaction before persistence, opaque source labels, retention metadata, and explicit run deletion.
- Includes ten MCP prompts that help users turn unclear product ideas into better UI-kit requests.
Built with Codex
I used Codex to plan the milestone architecture, implement FastMCP tools, iterate on the SQLite pipeline, add tests, harden capture and privacy behavior, and prepare Docker deployment and a judge-demo flow.
Judge quick start
The repository README includes local installation, Docker instructions, supported-platform notes, and a Railway deployment guide. The Docker image includes two self-authored demo screenshot inputs so judges can call the MCP tool without providing files from their own computer.
Log in or sign up for Devpost to join the conversation.