recipebooq
Server Details
Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 11 tools
The tools mostly have distinct scopes: discovery (find/get component), setup guidance, project mutation, proposal links, and verification are separable. However, the cluster around project edits and design handoff—add_screen, emit_app, install_component, propose_screen, propose_app, and update_components—requires careful reading to avoid misselection.
All names use snake_case with a clear verb_noun pattern: add_screen, find_component, get_component, install_component, verify_app, and so on. The minor singular/plural variation in update_components versus install_component is not enough to break the pattern.
Eleven tools is well-scoped for a design-to-Expo workflow spanning component discovery, setup guidance, app/screen generation, installation, updates, and verification. Each tool appears to serve a distinct phase rather than bloating the surface.
The surface covers the core lifecycle: find/get components, understand setup, propose designs, emit/add/install, update supplied files, scan snippets, and verify apps. Minor gaps exist around explicitly removing or uninstalling components/screens, but the main workflows are covered.
Available Tools
11 toolsadd_screenAdd a screen to an appARead-onlyIdempotentInspect
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.
Inputs: appId (required), tab, screen, manifest, +1 more.
check_snippetCheck code for blank-render bugsARead-onlyIdempotentInspect
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.
Inputs: code (required).
emit_appBuild an app from a designARead-onlyIdempotentInspect
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 step in full, which does not count against the daily allowance.
Inputs: appId (required), page, step, override.
find_componentFind a componentARead-onlyIdempotentInspect
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.
Inputs: need, category.
get_app_setupGet the app setupBRead-onlyIdempotentInspect
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.
Inputs: topic (required), platform.
get_componentGet a componentARead-onlyIdempotentInspect
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.
Inputs: slug (required), platform.
install_componentInstall a componentARead-onlyIdempotentInspect
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 "supabase", adds that integration: its files and the per-app wiring an export writes.
Inputs: slug (required).
propose_appPropose an app designAInspect
Your agent can design an app with you. Send it as app, a short plan or a full design, 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. format: true returns the format of a design, or of a plan beside app: { version: 1 }; "photos" lists sample photos. dryRun: true checks without making a link. into takes the code from the person's line and sends the design to the one they have open.
Inputs: app, into, dryRun, format.
propose_screenPropose a screen designAInspect
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; format: true returns the format. For a whole app, use propose_app.
Inputs: into, dryRun, format, composition.
update_componentsUpdate supplied componentsARead-onlyIdempotentInspect
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.
Inputs: manifest (required), page, current, acceptSplit.
verify_appVerify an emitted appARead-onlyIdempotentInspect
Needs a subscription. Checks an emitted app before a build: missing files, altered verbatim files, absent packages, expo-router's config merge, whether installed Xcode can build it, and whether a change needs a native rebuild.
Inputs: files (required), appId, config, toolchain, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android.
Visual builder for React Native and Expo apps. Read and update project design tokens.
Design mobile app screens with AI — describe your app, get linked screens instantly.
Design your mobile app UI with AI, then have your coding agent build the real app from it.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables an AI to see and operate an Expo / React Native app without an emulator, phone, or browser using real screenshots, taps, typing, scrolling, and automated bug hunting, with optional Android and iOS device control.961 npmMIT
- FlicenseAqualityDmaintenanceCreates new Expo React Native apps from a Feature-Sliced Design template and configures store deployment settings.3-

Sleek MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP clients to turn plain-language mobile app descriptions into rendered, editable screens and project links for exporting to Figma, HTML, or React.MIT- AlicenseAqualityDmaintenanceConverts a Figma file into a React project using Ant Design, AG Grid, ApexCharts, and Tailwind CSS, with optional export of mobile screens as a React Native (Expo) app.7MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.