bots.st/opointo
opointo
Turn UI specs into working Expo React Native app
3003 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 11
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://opointo.com/api/mcp
What it can do
| Tool | What it says it does |
|---|---|
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 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. |
check_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 clipped lens, a conditionally mounted surface. A read-only text scan, not a guarantee; verify_app checks a whole emitted project. |
emit_app | Needs a subscription. Turns a design from the Architect 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… |
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 own control is the right choice. Omit `need` to list every component with its purpose and whether it renders the real system control. |
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, 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. |
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 Android, the providers it needs at the app root, its dependencies, and the runtime rules that stop it rendering blank. |
install_component | Needs 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… |
propose_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 opens it in the Architect as a new, unsaved design. The person sees every screen, changes what they like, and hands it back for emit_app. into: the code in the… |
propose_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 back a link that opens it in the Architect as a new, unsaved design the person can change. into: as propose_app's. dryRun checks without making a link… |
update_components | Needs 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. |
verify_app | Needs 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. |
In its maker's words
Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android.
- Website
- opointo.com
- Source
- github.com/opointoHQ/opointo-mcp
- Publisher
- opointo.com
- Listed from
- the official MCP Registry as
com.opointo/opointo - Version
- 0.2.1, updated 27 Sep 2026
- Kinds of work
- Writing and translation, Code and developer tools, Browser and automation
The domain it lives on
- opointo.com
- registered 24 Sep 2026 (1 month ago), at Cloudflare, Inc., its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 3003 ms | |
| Answered | 2716 ms | |
| Answered | 1065 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.