Mobile Design MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOBBIN_API_KEY | No | API key for the Mobbin REST API, requiring the documented Team/Enterprise entitlement. | |
| MOBILE_DESIGN_DATA_DIR | No | Override the default user library directory. | ~/.local/share/mobile-design-mcp |
| MOBBIN_MCP_ACCESS_TOKEN | No | OAuth access token for the Mobbin MCP connection. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_provider_statusB | Inspect this local library and configured optional providers. No remote account checks. |
| refresh_awardsB | Fetch official Apple Design Awards and/or the dated Google Play Best of 2025 smartphone-app awards. Stores metadata, not screen libraries. |
| search_appsB | Search the local award/curated app catalog with FTS5. This is metadata search, not a full screen library. |
| get_appB | Read one local app reference, its sourced awards and associated local captures. |
| import_appC | Add a curated app reference without inventing awards. Use for your own apps or Android/iOS references. |
| import_recordingC | Copy a local screenshot/video into your owned reference library, hash it and retain platform/version provenance. |
| list_recordingsC | List imported local media, optionally with up to two inline screenshot previews. |
| create_flowB | Store an ordered reference journey backed by existing local recordings. Records observed steps, not an invented navigation trace. |
| get_flowC | Read an ordered reference flow and its capture provenance. |
| analyze_transitionB | Extract time-indexed review frames from a local video interval. Does not infer original easing, springs or haptics. |
| list_motion_recipesB | List authored native motion patterns, with SwiftUI and Jetpack Compose variants. |
| build_design_review_packetB | Create a bounded, revision-bound local snapshot for an independent native design review. Does not run reviewers or certify quality. |
| build_motion_recipeC | Generate an authored SwiftUI or Compose example with reduced-motion handling and explicit timing assumptions. |
| create_mobile_briefB | Synthesize a cited native-app direction from selected local references and flow evidence. Missing motion and visual evidence stay explicit. |
| create_project_briefC | Prepare a cited design direction for an explicit SwiftUI, Compose or Expo target. Does not infer capture stack or generate Expo motion recipes. |
| mobbin_search_screensB | Query the official Mobbin REST screen search live. Requires your API key; current native filter supports iOS, not Android. Results are not persisted. |
| mobbin_list_toolsA | Discover the official account-connected Mobbin MCP tool schemas. Requires OAuth sign-in. |
| mobbin_callB | Call a discovered, explicitly read-only official Mobbin MCP tool without persisting its content locally. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.