Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Nothing to run from here
recipebooq is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Look up @recipebooq/ui components: props, provider order, theme tokens, and the blank-render rules.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http recipebooq-mcp https://recipebooq.com/api/mcp
# 2 — ask your agent for something these tools do
# find_component, get_component, check_snippet and 8 more
recipebooq costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
REAll 1 server
recipebooq1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http recipebooq-mcp https://recipebooq.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| need | string | no | e.g. "a progress bar for an upload" |
| category | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | e.g. "button" |
| platform | string | no | only the rules that hold there |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | the TSX to check |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | — |
| platform | string | no | rules only |
Needs 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | the share code from the App Designer's "Send app to agent", e.g. "34ca4babb2" |
| override | boolean | no | emit even with screens flagged not ready; ask the customer first |
| step | string | no | a step id from the recipe, or "review" for the screen list |
| page | number | no | for step write or review; each page names the next |
Needs 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | yes | the share code from "Send app to agent" |
| screen | string | no | the new screen's name in that design |
| manifest | object | no | the parsed .opointo/files.json |
| tab | string | no | nest it in this tab's stack; omit to place it where the design does |
| componentName | string | no | only to add a second copy of a screen; omit for the export's name |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | e.g. "button", or a recipe id such as "supabase" |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| manifest | object | yes | the parsed .opointo/files.json (the object or its files array) |
| current | array | no | only when a split-unverified blocker asks: each named file's hash, from its command |
| acceptSplit | array | no | only once the customer agreed: the paths split-customer-edited blockers name |
| page | number | no | only when the answer's page.next asks for it |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| appId | string | no | the share code given to emit_app; appId in .opointo/files.json |
| files | array | yes | each file written, the hidden .opointo/files.json included: { path, bytes }, path from the project root |
| dependencies | array | no | package.json dependencies' keys |
| config | object | no | — |
| toolchain | object | no | — |
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 App Designer 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 person's line; it lands in their open design. dryRun checks without making a link; format: true ret
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | object | no | The design: { name, tabs: [{ screenId, label }], screens: [{ id, name, composition: { screen: { content: { children: [node] }, chrome: { header?, headerItems?, floating: [] }, overlays: [] } } }], onb |
| dryRun | boolean | no | check the design and report, without making a link |
| format | boolean/string | no | — |
| into | string | no | — |
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 App Designer 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| composition | object | no | One screen: { name, screen: { content: { children: [node] }, chrome: { header?, headerItems?, floating: [] }, overlays: [] } }. A node is { id, slug, props }: slug is "wireframe:<block>" or a componen |
| dryRun | boolean | no | check the screen and report, without making a link |
| format | boolean | no | — |
| into | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install recipebooq or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish recipebooq can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.