MCP servercom.recipebooq/recipebooq
Design a React Native app in a browser and emit it as a real Expo project you own, iOS and Android.
Overview
Score?
UNRATED 0.594
of what a free look can see, on 20 looks
Looks
21
last 8 days ago
Tools
14
changed 8 days ago
More info
URL
recipebooq.com/api/mcp
streamable-http
Says it is
opointo 0.2.0
protocol 2025-06-18
In the record since
29 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.594 · highest on record 0.8561
Toolsfrom sha256:0f26021b7c…9bbb92 · +0 −0 8 days ago
| Tool | Schema |
|---|---|
| add_screen PAID. Adds one new screen to an app that was already exported: the screen file, the route that mounts it, the exact line to register it, and how to navigate to it. Reads the .opoin |
input · no output |
| check_snippet Takes TSX that uses these components and returns the glass-safety problems in it: animated opacity, the flex:1 collapse, the clipped lens, the conditional mount. Read-only, it neve |
input · no output |
| emit_app PAID. Turns an opointo canvas into a working Expo app: navigation, providers, tab bar, screens and the components they need. Returns a recipe to apply to the current project: the e |
input · no output |
| emit_screen PAID. Turns one composed screen into a TSX file for an app that already exists, with its own navigator and routes. Returns the complete file inline, the components to install first |
input · no output |
| find_component Takes a UI need in plain language and returns ranked components, including an explicit answer when this catalog deliberately does not ship something and the OS's own control is the |
input · no output |
| get_component Everything needed to write a correct call site for one component: props with types, defaults and value domains, platform applicability, dependencies, and the runtime rules that app |
input · no output |
| get_provider_tree The exact app-root provider nesting these components require, in the order that works. Getting it wrong fails at runtime, not at compile time. Pass the components in use to see whi |
input · no output |
| get_rules The runtime rules for this catalog: the mistakes that make a component render blank or wrong with no warning, no error and no red box (on iOS, mostly native Liquid Glass). Pass a s |
input · no output |
| get_step FREE. Expands one step of an emit_app recipe: the full instruction, why it matters, how to know it worked, and what to do when it did not. emit_app returns steps in short form to s |
input · no output |
| get_theme_tokens The theme system: which hooks to call, and the spacing, radius and typography scales. Token names rather than hex values are what let a retheme propagate. |
input · no output |
| install_component PAID. Adds one component to an existing project. Returns the transitive registry closure in dependency-first install order, the single `expo install` line for the whole closure, ev |
input · no output |
| list_components Lists the shipped @opointo/ui components: slug, purpose, category, and which render the real iOS system control versus our own component. Cheap, and a good first call. Optional fil |
input · no output |
| update_components PAID. Reports what has changed in the opointo-supplied files since export and returns only what moved. Reads the .opointo/files.json the export wrote into the project, so no share |
input · no output |
| verify_app PAID. Checks that an emitted app was applied correctly, before it is built. Takes what was written (file paths with byte sizes, package.json dependencies, project config, build too |
input · no output |
Verify it yourself
npx teppi-check https://recipebooq.com/api/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1RE4RDY3F6EHTVWTRKWQARH