
Mockups Gallery
Self-host a mockups gallery with MCP access so your agent can list, retrieve, and iterate AI-generated UI mockups before you commit engineering time.
Overview
Mockups Gallery is a Validate-phase self-hosted MCP server that exposes an AI-generated mockups gallery to coding agents over HTTP, SSE, or containerized stdio.
What is this MCP server?
- Self-hosted Mockups Gallery with MCP endpoints for AI-generated UI mockups
- Remote streamable-http and SSE transports at https://{host}/mcp and /mcp/sse
- OCI container ghcr.io/kgnatx/mockups-mpc:1.2.2 plus stdio-oriented packaging
- Version 1.2.2 from kgNatx/mockups-mpc GitHub source
- Published version 1.2.2 (OCI ghcr.io/kgnatx/mockups-mpc:1.2.2)
- Two remote MCP URLs: /mcp (streamable-http) and /mcp/sse (SSE)
- Self-hosted architecture with GitHub source mockups-mpc
Community signal: 2 GitHub stars.
What problem does it solve?
AI mockups pile up in local folders where your agent cannot browse, compare, or reference them during prototype validation.
Who is it for?
Indie founders validating UI direction with heavy AI mockup generation who want agent-readable gallery access on their own domain.
Skip if: Teams wanting a hosted SaaS design tool with no self-hosting, or pure code-only backends with no visual prototype step.
What do I get? / Deliverables
After you host the gallery and register MCP remotes, your agent pulls mockups from a stable gallery URL while you narrow UX and scope.
- Agent-queryable gallery of AI-generated mockups on infrastructure you control
- HTTP/SSE MCP endpoints at /mcp and /mcp/sse for remote IDE access
Recommended MCP Servers
Journey fit
Canonical shelf is Validate because the server supports visual prototyping and stakeholder-ready artifacts ahead of full Build. prototype fits a gallery plus MCP tools that let agents browse and pull mockup assets during scope and UX validation.
How it compares
Self-hosted mockup gallery MCP, not a component library skill or a generic image CDN integration.
Common Questions / FAQ
Who is mockups-gallery for?
Solo builders and designers shipping fast who self-host AI mockups and want Claude Code, Cursor, or similar agents to read that gallery via MCP.
When should I use mockups-gallery?
Use it in Validate and prototype when you need shareable mockup iterations and agent-driven retrieval before locking frontend implementation.
How do I add mockups-gallery to my agent?
Deploy ghcr.io/kgnatx/mockups-mpc:1.2.2, set your host in MCP config using https://{host}/mcp or /mcp/sse, or wire the OCI stdio package per your client’s docs.