Skip to content
Official MCP RegistryListed

opointo

Part ofopointolisted on 2 directories

Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android.

First seen 2 Oct 2026. Evidence as of 7 Oct 2026.

11
Tools
From an anonymous probe
1
Source listings
Each with its own history
13
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
add_screenNeeds a subscription. Adds one screen designed in the App Designer to a project. With the project's .opointo/files.json it returns the screen file, the route that mounts it and the one line to register it, and never rewrites existing files. Without it, a self-contained screen file for any Expo app.Read-only
check_snippetScans TSX that uses these components for the mistakes that render nothing with no error: animated opacity on glass, the flex: 1 collapse, a clipped lens, a conditionally mounted surface. A read-only text scan, not a guarantee; verify_app checks a whole emitted project.Read-only
emit_appNeeds a subscription. Turns an App Designer design into a working Expo app: navigation, providers, tab bar, screens and the components they use. Returns a recipe for the current project: every file with its target path, one install line and ordered steps with a check each. Pass `step` for one step in full, which does not count against the daily allowance.Read-only
find_componentFinds the component for a UI need described in plain words, ranked, and says when this catalog ships nothing on purpose because the phone's own control is the right choice. Omit `need` to list every component with its purpose and whether it renders the real system control.Read-only
get_app_setupHow 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, the theme hooks and token scales, or the rules that hold across the whole catalog. An app built by emit_app already has all three wired.Read-only
get_componentEverything needed to write a correct call site for one component: props with types, defaults and allowed values, what draws on iOS and on Android, the providers it needs at the app root, its dependencies, and the runtime rules that stop it rendering blank.Read-only
install_componentNeeds a subscription, except for the free foundation components. Adds one component to an existing project: the files it and its dependencies need in install order with exact target paths, the single expo install line, the providers it needs and its runtime rules. A backend recipe's id, such as "supabase", adds that integration: its files and the per-app wiring an export writes.Read-only
propose_appYour 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 opens it in the App Designer as a new, unsaved design. The person sees every screen and the navigation, changes what they like, and hands it back for emit_app. Each problem comes back with its path and a fix. dryRun checks without making a link; format: true returns the format and every block, or with app: { version: 1 } a short plan's.Changes data
propose_screenYour agent can design a single screen with you: send one screen in opointo's design format (the Composition add_screen builds from) and get back a link that opens it in the App Designer as a new, unsaved design the person can change. Each problem comes back with its path and a fix. dryRun checks without making a link; format: true returns the format. For a whole app with navigation, propose_app is the matching tool.Changes data
update_componentsNeeds a subscription. Reads the project's .opointo/files.json and returns only the opointo-supplied files that changed since export, so it works months later with no share code. Never touches the customer's own screens, and flags the rare change that needs a code edit rather than a copy.Read-only
verify_appNeeds a subscription. Checks an emitted app before it is built: missing files, altered verbatim files, absent packages, the expo-router config merge, whether the installed Xcode can build it, and whether a change needs a new native build.Read-only

Change history

  1. verify_app: input schema changed
  2. verify_app: description changed (+"verbatim" +"expo-router" +"merge,")
  3. propose_app: description changed (+"block, or with app: { version: 1 } a short plan's." -"block.")
  4. verify_app: input schema changed
  5. update_components: input schema changed (+page)
  6. propose_screen: description changed (+"Designer" -"Builder")
  7. propose_app: description changed (+"Designer" -"Builder")
  8. install_component: input schema changed
  9. install_component: description changed (+"A backend recipe's id, such as "supabase", adds that integration: its files and the per-app wiring an export writes.")
  10. emit_app: input schema changed
  11. emit_app: description changed (+"Designer" -"Builder")
  12. add_screen: description changed (+"Designer" -"Builder")
  13. server instructions changed (+"Designer" -"Builder")
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registrycom.opointo/opointo2 Oct 20267 Oct 20261