Mobile Design MCP
Related Servers
Alternatives to Mobile Design MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEquips coding agents with curated design rules, art directions, UI audits, component discovery, and reference guides so they can produce less generic, more polished interfaces in Claude Code, Codex, Cursor, and other MCP clients.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to research design references per page section across galleries like Awwwards, Dribbble and Mobbin, render the user's page in multiple style directions with live 3D components, and collect votes on a local board. It then produces a PDF report and iteratively builds and refines the actual page, dashboard prototype or mobile screens from that feedback.943 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables users to search and browse Mobbin's extensive library of mobile app designs, screenshots, and user flows directly from Claude. It allows for detailed exploration of UI patterns, elements, and personal collections using reverse-engineered API access.47ISC
- AlicenseBqualityBmaintenanceEnables AI coding agents to absorb UI references into perceptual design tokens, semantic responsive layout skeletons, motion physics parameters, and zero-dependency multi-framework components, while auditing WCAG contrast, touch targets, reduced-motion guardrails, and layout stability.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables coding agents to turn CollectUI links or any image/GIF/video URL into a detailed design and motion brief with measured timings, easing curves, displacement, palette, and opt-in keyframes.16 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to ground UI work in real product screens by returning concrete screen references, design references, and licensed fonts, icons, or animated icons on request. It also ships a bundled design workflow, command playbooks, and connection diagnostics that work without an API token.-
TDQS
Scored across 18 tools
Most tools target distinct resources or operations, and descriptions clarify local versus remote behavior. The main soft overlaps are among brief/review creation tools (create_mobile_brief, create_project_brief, build_design_review_packet) and the Mobbin discovery/call trio, but boundaries are still mostly readable.
The set is consistently snake_case and mostly follows a verb_noun pattern such as get_app, import_recording, create_flow, and build_motion_recipe. Minor deviations like mobbin_call and occasional verb variation (create vs build) are understandable rather than confusing.
Eighteen tools is on the heavy side for a focused mobile design reference server. The set covers several subdomains (local catalog, media, flows, motion recipes, briefs, and Mobbin), making it borderline rather than clearly well-scoped.
Core creation and retrieval paths exist, but lifecycle coverage is uneven: there are create/get tools for flows but no list_flows, and apps, recordings, recipes, and briefs lack update/delete operations. These are notable gaps for managing a reference library, though agents can work around some of them.