Skip to main content
Glama

Mobile Design MCP — Design that feels native. Original vector illustration.

Mobile Design MCP

From inspiration to a native app you can actually inspect.

A mobile design toolkit for Claude Code and Codex: reference research, purposeful visual systems, SwiftUI / Jetpack Compose / Expo implementation, independent reviews and explicit UX/performance evidence.

For noncommercial studies, learning and research. Original code uses the Noncommercial Study License. Marked Apache-2.0 files retain their permissions. No runtime license locks. Rights and scope.

10 skills · 7 reviewer profiles · 18 MCP tools · Windows / macOS / Linux

See the native comparison · Usage, commands and triggers · Install for your client · Explore the workflow

This is an early working toolkit. It supports an agent's design work; it does not certify award quality, collect native frame profiles or turn one screenshot into a complete app.

Original iOS and Expo studies

Two standalone SwiftUI apps demonstrate editing, native reordering, undo, state-backed feedback and SVG export. Folio adds an original Expo / React Native reading queue. Each app includes a baseline/refined treatment of the same task and content. Open the studies and motion gallery for source, run instructions, actual captures and verification limits.

Related MCP server: collectui

A small app, two design approaches

Tempo is a real Jetpack Compose habit-completion study. Both screenshots come from the same Android emulator and APK, with the same three habits and one already complete.

The redesign gives the next task a specific action, groups related information, applies a small type/spacing system, and connects native progress feedback to actual state. The MCP supplied reference metadata, a brief and an authored motion recipe; the agent wrote and compiled the app.

This is an illustrative redesign, not an independent-agent benchmark or a measured UX improvement. Both variants were made by one author, who knew the workflow. Provider gaps and unmeasured checks remain visible. The banner above is an illustration; the comparison images are unedited emulator screenshots.

Run the mini app · Read the evidence and limitations · Capture metadata

Quick start

Requires Node.js 22.13 or newer. Video analysis also requires ffmpeg and ffprobe.

The toolkit targets Windows, macOS and Linux, primarily through Claude Code and Codex. See client installation and capability boundaries. Native build/editor prerequisites still depend on the target platform.

git clone https://github.com/noxpublishing/mobile-design-mcp.git
cd mobile-design-mcp
npm ci --ignore-scripts
npm run build
npm run index

The index command fetches public award metadata. The MCP server does not crawl automatically at startup. Default user library: ~/.local/share/mobile-design-mcp; override it with MOBILE_DESIGN_DATA_DIR.

Start the stdio MCP process directly with:

node dist/cli.js

For Codex:

codex mcp add mobile_design -- node /absolute/path/to/mobile-design-mcp/dist/cli.js

Use a longer tool deadline for video work; see configuration example and official MCP documentation.

Design workflow

flowchart LR
  A[Goal and users] --> B[Mobbin and Awwwards references]
  B --> C[Comparable design directions]
  C --> D[Chosen native visual system]
  D --> E[Build and independent review]
  E --> F[UX refinement]
  F --> G[Measured native performance]
  G --> H[Optional app showcase]

The working agent keeps the brief and decisions coherent. Independent reviewers receive fresh conversation contexts and bounded evidence for a particular question. They judge visible or measured results rather than inheriting the author's explanation.

The workflow contract defines:

  • Small role-based typography scales and named spacing relationships.

  • Purposeful heading treatment, hierarchy and placement.

  • Consistency without turning every screen into the same template.

  • Proportionate reviews for a local edit, flow change or new direction.

  • Revision-bound evidence and targeted reruns after accepted changes.

  • Separate design, UX, performance and qualified-handoff outcomes.

The app's existing native themes and components remain authoritative. Review snapshots do not become another editable token database. Missing device access or profiles remain unverified work, not a passing score.

Skills

Skill

Purpose

mobile-setup

Short initial interview, project scope/style and a durable preparation record

mobile-design

Reference-led native design, independent review and final UX/performance loops

mobile-expo

Design, audit and refine the actual Expo / React Native project

mobile-quality

Review hierarchy, task actions, typography, recovery and native accessibility

mobile-project-docs

Useful READMEs and consistent AGENTS.md/CLAUDE.md with one canonical project context

mobile-design-spec

Implementation-ready task/state, visual-system and motion contracts

mobile-design-drift

Evidence-based consistency audit across decisions, source, renders and docs

mobile-figma

Selected Figma context, assets/mappings and native implementation comparison

mobile-motion

Native animation implementation and optional Rive authoring/integration

mobile-showcase

A separate product website using final app screenshots and clips after app completion

Install all eight skills and seven reviewer definitions for both clients with the portable Node installer:

node scripts/install-workflow.mjs --client both --scope user

It uses real copies without symlink privileges, preserves unmanaged/modified destinations, and does not change permissions, models or account connections. See client options for per-project installation and update behavior. Start with $mobile-setup in Codex or /mobile-setup in Claude Code. The reviewer profiles are used on relevant evidence in fresh contexts; they do not run merely because they are installed.

The mobile server exposes 18 tools. Figma and Rive are optional external client connections, documented in Figma and Rive. Read the motion pipeline for how references become native code or actual Rive assets and verified app behavior.

MCP tools

Tool

Capability

get_provider_status

Local catalog and optional provider/dependency readiness

refresh_awards

Official Apple and/or dated Google Play award metadata

search_apps, get_app

Search/read award and curated app references

import_app

Add a curated reference without inventing awards

import_recording, list_recordings

Validate, copy and hash local screenshots or videos

create_flow, get_flow

Annotate ordered reference steps with valid clip bounds

analyze_transition

Extract time-indexed review frames; reuse valid cached studies

build_design_review_packet

Snapshot bounded local design evidence for independent review

list_motion_recipes, build_motion_recipe

SwiftUI/Compose examples with explicit timing and reduced-motion behavior

create_mobile_brief

Legacy native V1 brief

create_project_brief

Explicit OS/stack V2 brief, including Expo / React Native

mobbin_search_screens

Live official REST search, with its own account entitlement

mobbin_list_tools, mobbin_call

Discover and call explicitly read-only official MCP tools

The current server exposes 17 tools. Motion examples cover bottom sheets, shared elements and success feedback on both native platforms. They are authored examples, not recovered source or device-verified app builds.

Evidence and review packets

Imported media retains content hashes separately from capture context. Identical bytes can belong to different app versions or capture circumstances; those contexts get separate records. Reference, proposed and implemented journeys must remain distinguishable.

Place a review manifest at the native project root and add actual project-local captures. Call build_design_review_packet with absolute manifest/output paths and a mode: consistency, discoverability, motion, accessibility or performance.

The packet builder:

  • Checks declared revision/hash consistency and local path boundaries.

  • Copies at most eight evidence assets, 8 MiB per asset and 20 MiB of evidence in total.

  • Separately includes up to eight design-source snapshots of at most 128 KiB each.

  • Includes canonical design-source snapshots for consistency checks.

  • Withholds rationale, rules and reference examples in discoverability mode.

  • Marks missing required evidence inconclusive.

  • Does not start reviewers, establish build identity or certify UX/performance.

A frame interval is not a measured transition duration. Haptics, gesture timing and original easing/spring parameters remain unknown without supporting evidence. The performance run template starts explicitly unmeasured; native collectors must supply real profiles.

Awwwards is consulted through an available external MCP or normal web research. This server does not bundle an Awwwards connection. iOS simulator builds/profile collection require a suitable Mac/Xcode environment; recordings can be imported on another host.

Mobbin connection

The local library and native tools work without Mobbin. To connect your own eligible account:

npm run mobbin:login

The explicit login command displays an authorization URL and listens on a loopback callback. It uses the official OAuth flow with PKCE and state checking, and saves credentials with private file permissions in the user library. A real account is required to verify access.

A supplied OAuth token can alternatively use MOBBIN_MCP_ACCESS_TOKEN. REST uses a different credential, MOBBIN_API_KEY, and its documented Team/Enterprise entitlement. An .env file is not loaded automatically; provide variables through the server's launch environment.

The current REST schema supports ios and web, not Android. This native toolkit exposes the iOS subset and rejects Android REST requests before sending them. MCP tools are discovered from the connected account; the bridge forwards only tools explicitly annotated read-only.

Provider answers remain live and are not copied into the local reference corpus. See connection details, source boundaries and the providers' own terms.

Verification and limits

npm test
npm run smoke

Tests run offline, including media/provenance, FTS, flow bounds, platform diagnostics, native recipes, OAuth storage and review packet isolation. Video tests need ffmpeg/ffprobe.

The smoke test starts the real stdio MCP server, uses temporary local state and fetches the public award sources live. Its generated report goes to ignored .artifacts/live-smoke.json. It does not imply an authenticated Mobbin test or native rendering/profiling.

Apple Design Awards and Google Play Best of are different recognitions. Google Play remains labeled as a broad app award with region/year, not a UI-design prize. Award metadata does not include current screens or measured animations.

The independent workflow review and resulting changes are summarized in review notes. Native UI rendering, real-user research and final app performance verification must still be performed for each actual app project.

License and acknowledgments

Original runtime code and unmarked project documentation use the custom Noncommercial Study License. You may inspect, modify and redistribute them for the permitted study purposes, retaining the license and notices. Commercial use by recipients requires separate permission. This is a public, source-available project; it is not offered as unrestricted open-source software.

Adapted workflow files explicitly marked Apache-2.0 retain that license and its permissions. Dependencies and reference content retain their own rights. See NOTICE, Apache license and usage and content rights. A study label does not clear rights in third-party screens, graphics, fonts or brands.

Available Tools

18 tools
analyze_transitionB

Extract time-indexed review frames from a local video interval. Does not infer original easing, springs or haptics.

Inputs: endMs (required), startMs (required), recordingId (required), frames, +1 more.

build_design_review_packetB

Create a bounded, revision-bound local snapshot for an independent native design review. Does not run reviewers or certify quality.

Inputs: mode (required), manifestPath (required), outputDirectory (required).

build_motion_recipeC
Read-onlyIdempotent

Generate an authored SwiftUI or Compose example with reduced-motion handling and explicit timing assumptions.

Inputs: pattern (required), platform (required), durationMs, reducedMotion.

create_flowB

Store an ordered reference journey backed by existing local recordings. Records observed steps, not an invented navigation trace.

Inputs: steps (required), title (required), platform (required), tags, +1 more.

create_mobile_briefB
Read-onlyIdempotent

Synthesize a cited native-app direction from selected local references and flow evidence. Missing motion and visual evidence stay explicit.

Inputs: goal (required), platform (required), appIds, flowIds, +1 more.

create_project_briefC
Read-onlyIdempotent

Prepare a cited design direction for an explicit SwiftUI, Compose or Expo target. Does not infer capture stack or generate Expo motion recipes.

Inputs: goal (required), target (required), appIds, flowIds, +1 more.

get_appB
Read-onlyIdempotent

Read one local app reference, its sourced awards and associated local captures.

Inputs: id (required).

get_flowC
Read-onlyIdempotent

Read an ordered reference flow and its capture provenance.

Inputs: id (required).

get_provider_statusB
Read-onlyIdempotent

Inspect this local library and configured optional providers. No remote account checks.

Inputs: no named parameters.

import_appC

Add a curated app reference without inventing awards. Use for your own apps or Android/iOS references.

Inputs: name (required), platforms (required), tags, sourceUrl, +1 more.

import_recordingC

Copy a local screenshot/video into your owned reference library, hash it and retain platform/version provenance.

Inputs: path (required), title (required), platform (required), tags, +4 more.

list_motion_recipesB
Read-onlyIdempotent

List authored native motion patterns, with SwiftUI and Jetpack Compose variants.

Inputs: no named parameters.

list_recordingsC
Read-onlyIdempotent

List imported local media, optionally with up to two inline screenshot previews.

Inputs: appId, limit, platform, previews.

mobbin_callB
Read-only

Call a discovered, explicitly read-only official Mobbin MCP tool without persisting its content locally.

Inputs: name (required), arguments.

mobbin_list_toolsA
Read-only

Discover the official account-connected Mobbin MCP tool schemas. Requires OAuth sign-in.

Inputs: no named parameters.

mobbin_search_screensB
Read-only

Query the official Mobbin REST screen search live. Requires your API key; current native filter supports iOS, not Android. Results are not persisted.

Inputs: query (required), platform (required), limit.

refresh_awardsB

Fetch official Apple Design Awards and/or the dated Google Play Best of 2025 smartphone-app awards. Stores metadata, not screen libraries.

Inputs: year, provider.

search_appsB
Read-onlyIdempotent

Search the local award/curated app catalog with FTS5. This is metadata search, not a full screen library.

Inputs: limit, query, platform, awardsOnly.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 18 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables 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.
      47
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      -