recipebooq is a remote MCP server that gives an AI agent 14 tools, among them add_screen, check_snippet, emit_app. It answers at https://recipebooq.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Look up @recipebooq/ui components: props, provider order, theme tokens, and the blank-render rules.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
add_screen | PAID. Add 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 .recipebooq/files.json manifest to work out the route tree — it nev Inputs: compositionId, manifest, tab, componentName |
check_snippet | Paste TSX that uses these components and get back the glass-safety problems in it — the animated opacity, the flex:1 collapse, the clipped lens, the conditional mount. Read-only: it never touches your repo. A heuristic text scan, not a stru Inputs: code |
emit_app | PAID. Turn a recipebooq canvas into a working app: navigation, providers, tab bar, screens and the components they need. Returns a recipe — the exact files with their target paths, the dependency install line, and ordered steps — to apply t Inputs: appId, override |
emit_screen | PAID. Turn one composed screen into a real TSX file you can drop into an app you already have — your navigator, your routes. Returns the complete file inline, the components to install first, and how to mount it. Use emit_app instead when t Inputs: compositionId, componentName |
find_component | Describe a UI need in plain language and get ranked components — including an explicit answer when this catalog deliberately does NOT ship something and you should use the OS's own control instead. Call this before building any UI control b Inputs: need |
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 apply to it. Always read the rules; getting props right and ru Inputs: slug |
get_provider_tree | The exact app-root provider nesting these components require, in the order that works. Getting this wrong fails at runtime, not at compile time. Optionally pass the components you are using to see which providers they each need. Inputs: components |
get_rules | The runtime rules for this catalog — the mistakes that make native Liquid Glass render blank with no warning, no error and no red box. Pass a slug to scope them to one component. Read these before writing animation or layout code against an Inputs: slug |
get_step | FREE. Expand 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 stay inside the response budget — call this before any step yo Inputs: appId, stepId |
get_theme_tokens | The theme system: which hooks to call, and the spacing, radius and typography scales. Reference token names rather than hex values so a retheme propagates. |
install_component | PAID. Add one component to an existing project, correctly. Returns the transitive registry closure in dependency-first install order, the single `expo install` line for the whole closure, every file with its exact target path, the provider Inputs: slug |
list_components | List the shipped @recipebooq/ui components — slug, purpose, category, and which are real iOS system controls vs. our own glass. Call this first; it is cheap. Optionally filter by category or tech. Inputs: category, tech |
update_components | PAID. Tell the customer what has changed in their recipebooq files since they exported, and hand back only what moved. Reads the .recipebooq/files.json the export wrote into their project — no share code needed, so it works months later. Ne Inputs: manifest |
verify_app | PAID. Check that an emitted app was actually applied correctly, before building it. Report what you wrote — file paths with byte sizes, your package.json dependencies, and the project config — and get back what is missing, which copy-verbat Inputs: appId, files, dependencies, config |
Every block below points at https://recipebooq.com/api/mcp. Pick your client and copy.
claude mcp add --transport http recipebooq https://recipebooq.com/api/mcp
{
"mcpServers": {
"recipebooq": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://recipebooq.com/api/mcp"]
}
}
}{
"mcpServers": {
"recipebooq": {
"url": "https://recipebooq.com/api/mcp"
}
}
}{
"servers": {
"recipebooq": {
"type": "http",
"url": "https://recipebooq.com/api/mcp"
}
}
}{
"context_servers": {
"recipebooq": {
"url": "https://recipebooq.com/api/mcp"
}
}
}{
"mcpServers": {
"recipebooq": {
"serverUrl": "https://recipebooq.com/api/mcp"
}
}
}{
"mcpServers": {
"recipebooq": {
"url": "https://recipebooq.com/api/mcp"
}
}
}name: recipebooq
version: 0.0.1
schema: v1
mcpServers:
- name: recipebooq
type: streamable-http
url: https://recipebooq.com/api/mcp{
"mcpServers": {
"recipebooq": {
"httpUrl": "https://recipebooq.com/api/mcp"
}
}
}{
"mcpServers": {
"recipebooq": {
"type": "http",
"url": "https://recipebooq.com/api/mcp"
}
}
}{
"mcpServers": {
"recipebooq": {
"url": "https://recipebooq.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Frecipebooq.com%2Fapi%2Fmcp&type=streamable_http&id=recipebooq&name=recipebooq
It answered our last check on 19 October 2026 in 1106 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by recipebooq.com and served from recipebooq.com, the vendor's own domain: https://recipebooq.com/api/mcp.
14, as returned by the server's own tools/list on 11 September 2026: add_screen, check_snippet, emit_app, emit_screen, find_component, get_component, get_provider_tree, get_rules, and 6 more.
It answered our last check on 19 October 2026 in 1106 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://recipebooq.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.recipebooq. Endpoint host: recipebooq.com. ARD identifier: urn:air:com.recipebooq:mcp:recipebooq.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.