Categories › Software Development › Frontend, UI components & design-to-code
Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android.
Remote server: your requests and data go to opointo.com. Claude Code: claude mcp add --transport http opointo https://opointo.com/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
find_component — Finds the component for a UI need described in plain words, ranked, and says when this catalog ships nothing on purpose because the phone's get_component — Everything needed to write a correct call site for one component: props with types, defaults and allowed values, what draws on iOS and on Ancheck_snippet — Scans TSX that uses these components for the mistakes that render nothing with no error: animated opacity on glass, the flex: 1 collapse, a get_app_setup — How an app is set up so these components work and follow its theme, one topic at a time: the app-root providers in the order that works, theemit_app — Needs a subscription. Turns a design from the Architect into a working Expo app: navigation, providers, tab bar, screens and the components add_screen — Needs a subscription. Adds one screen designed in the Architect to a project. With the project's .opointo/files.json it returns the screen finstall_component — Needs a subscription, except for the free foundation components. Adds one component to an existing project: the files it and its dependencieupdate_components — Needs a subscription. Reads the project's .opointo/files.json and returns only the opointo-supplied files that changed since export, so it wverify_app — Needs a subscription. Checks an emitted app before a build: missing files, altered verbatim files, absent packages, expo-router's config merpropose_app — Your agent can design an app with you: send an app in opointo's design format (the AppSpec emit_app builds from) and get back a link that oppropose_screen — Your agent can design a single screen with you: send one screen in opointo's design format (the Composition add_screen builds from) and get Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.