Searchable real-screen catalogue
Query curated iOS app screens and web interface packs over MCP so layout hierarchy and density start from real products rather than guesswork.
Developer tooling · Hosted MCP server & UI skill Active system
Niblet MCP is a hosted Model Context Protocol server and open-source UI design skill built by PyModel LLC at niblet.pymodel.com. It grounds coding agents in a searchable catalogue of real iOS and web product screens, enforces repository token reuse, and verifies rendered UI states before completion.
Built for: Frontend engineers, product designers, and teams using Claude Code, Codex, Cursor, or MCP-enabled coding agents.
Reference-grounded interface engineering
When coding agents build or restyle an interface without visual references, they converge on the same interchangeable card grids, invented color tokens, and happy-path-only screens—ignoring the components already in the repository and skipping empty, loading, offline, and validation states.
PyModel LLC built Niblet MCP (niblet.pymodel.com) to close that gap inside the agent loop. Through a remote MCP server, REST API, and the open-source @pymodel/niblet skill, an agent searches real product screen patterns by intent, writes a short design contract tied to the codebase’s existing tokens, implements every reachable UI state, and inspects the rendered viewport before reporting done.
Live at niblet.pymodel.com with open-source skill packages at github.com/PyModel/niblet-skill-mcp.
Query curated iOS app screens and web interface packs over MCP so layout hierarchy and density start from real products rather than guesswork.
Anchor typography, spacing, surfaces, and components to the tokens already defined in your repo before writing new styles.
Enumerate and build empty, loading, validation-error, permission, and narrow-viewport states alongside the primary view.
Close every UI task by checking contrast, alignment, overflow, and interactive targets against the live rendered output.
UI agent workflow comparison
Why structured MCP visual retrieval and design contracts outperform ad-hoc prompting.
| Workflow Step | Niblet MCP (@pymodel/niblet) | Ungrounded Prompt-Only UI | Manual Screenshot Pasting |
|---|---|---|---|
| Visual reference source | On-demand MCP search across structured iOS and web product screen packs | Model training-set averages (repetitive SaaS card clichés) | Manual hunting and cropping by the developer on every prompt |
| Design-system fidelity | Reads and reuses existing repo tokens, components, and spacing scales first | Frequently invents parallel hex values and duplicate wrapper classes | Copies external visual styles that clash with the host product |
| Reachable UI states | Explicit contract requiring empty, loading, error, and responsive states | Usually ships only the populated desktop happy path | Limited to whichever single state appeared in the pasted image |
| Completion gate | Rendered inspection check before marking interface work finished | Stops as soon as TypeScript or CSS compiles without viewing the page | Requires back-and-forth human visual QA rounds for basic layout bugs |
Direct answers
Architecture write-ups, adjacent products, and delivery services from PyModel LLC.
Share your current architecture, data boundaries, and target outcome with our engineering team.