A recipe is a reusable catalog section or page that Orbit inserts into an existing workspace.

## Recipes add content to a workspace

Use a recipe when a catalog section or page fits the screen you need with few changes. You select a recipe by its catalog slug and choose the target workspace.

Orbit creates the recipe's nodes on the server and validates each node. For a page recipe, Orbit places the content under the existing Page root. A node is an element in the app's page structure.

The [Orbit MCP server card](https://mcp.orbitapps.io/.well-known/mcp/server-card.json) defines **Apply recipe** and the results it returns.

## A check is different from an insertion

**Apply recipe** supports a dry run. A dry run checks the request without inserting the recipe. Its response includes `issues` and `warnings` for you to inspect.

An application response includes `applied` and `node_ids`. An `applied` value of `true` confirms that Orbit applied the recipe. The returned `node_ids` identify the content Orbit created.

Node validation does not prove that a page meets your needs. Inspect the page in **Mockup** after you apply the recipe.

## A successful insertion is not a finished page

Suppose your tasks page needs a section headed ‘Upcoming tasks’. This is an example, not a catalog recipe name. A recipe may provide a suitable layout, but a successful application does not prove that the inserted text and layout fit your tasks page.

Follow [Apply a recipe](/guides/apply-a-recipe) for catalog lookup, dry runs, application, and retries. See [Edit a mockup](/guides/edit-a-mockup) to change the inserted content.