Integration

BigOven integration

BigOven Build API gives read access to BigOven's archive of over a million recipes. Search recipes by keyword, title, ingredient, category, cuisine, cooking time or ingredient count, read a recipe's full detail (ingredients with US and metric quantities, instructions, yield, timings, nutrition on plans that include it), find related recipes, browse curated seasonal collections and recipe categories, autocomplete titles, and read a recipe's photos, reviews and review replies. Every tool is read-only and works on public data: the grocery list, profile, recipe notes, recently viewed recipes, recipe and review writing and photo upload routes act as a signed-in BigOven user through a second Basic credential and are not exposed, nor are the editors-only feedback route and the routes BigOven marks deprecated. Authentication is the API key from the BigOven Build API console (paid plans from $99 a month), sent in the X-BigOven-API-Key header; BigOven's terms forbid keeping its data for more than 30 minutes.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in BigOven.Built from the 17 BigOven tools below, on the connection you add once.

What you can do with BigOven

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Recipe, 3 operations

  • get_recipeGet recipeGETAgents: ask firstReturns one recipe in full: title, description, category and cuisine, ingredients (name, quantity and unit in US and metric, department), instructions, yield, total and active minutes, star rating, review and favorite counts, poster.
  • get_recipe_with_videosGet recipe with videosGETAgents: ask firstReturns the same full recipe as get_recipe plus its videos, when BigOven has any. Set includeInstructions to true to have the instructions included (they are left out by default).
  • search_recipesSearch recipesGETAgents: ask firstSearches BigOven's recipes and returns one page of matches (RecipeID, title, category, cuisine, star rating, review count, servings, photo and BigOven page URL) with the total ResultCount.

Collection, 2 operations

  • list_collection_recipesList collection recipesGETAgents: ask firstReturns one page of the recipes in a curated collection, in the same shape as search_recipes results.
  • list_collectionsList collectionsGETAgents: ask firstLists BigOven's current seasonal and curated recipe collections (ID, title, description, photo and web URL). Pass a collection ID to list_collection_recipes for its recipes.

Review, 2 operations

  • get_reviewGet reviewGETAgents: ask firstReturns one review by its ID: comment, star rating, total and active minutes, poster, creation date, reply count and the featured reply.
  • list_recipe_reviewsList recipe reviewsGETAgents: ask firstReturns one page of a recipe's top-level reviews, each with its comment, star rating, poster, reply count and at most one featured reply. Pass a review ID to list_review_replies for the full thread.

All, 1 operation

  • autocomplete_recipesAutocomplete recipesGETAgents: ask firstAutocompletes a partial recipe title across all recipes and returns the matching recipes, each with its RecipeID, title, image URL, servings and quality score, for a type-ahead that leads straight to get_recipe.

Autocomplete, 1 operation

  • autocomplete_recipe_titlesAutocomplete recipe titlesGETAgents: ask firstReturns recipe titles that start with the given text (at least 3 characters), for a type-ahead search box. Titles only; use autocomplete_recipes to also get recipe ids.

Categorie, 1 operation

  • list_recipe_categoriesList recipe categoriesGETAgents: ask firstLists BigOven's recipe categories with their ID, name and parent category. A category ID can be passed to the include_cat or exclude_cat filter of search_recipes.

Meta, 1 operation

  • get_collectionGet collectionGETAgents: ask firstReturns a curated collection's metadata: title, description, photo, web and mobile URLs and whether it is a PRO collection.

Photo, 1 operation

  • list_recipe_photosList recipe photosGETAgents: ask firstReturns one page of the photos posted for a recipe, with the total count. Any BigOven photo URL can be resized by appending h and w query values (for example ?h=64&w=64).

Random, 1 operation

  • get_random_recipeGet random recipeGETAgents: ask firstReturns one random recipe of home-page quality, with its ingredients, instructions, timings, rating and photo.

Rave, 1 operation

  • list_recipe_ravesList recipe ravesGETAgents: ask firstReturns one page of raves: pairs of a recipe summary (RecipeInfo) and a 4 or 5 star review of it (Review).

Related, 1 operation

  • list_related_recipesList related recipesGETAgents: ask firstReturns one page of recipes BigOven considers related to the given recipe, in the same shape as search_recipes results.

Replie, 1 operation

  • list_review_repliesList review repliesGETAgents: ask firstReturns one page of the replies posted under a review, each with its comment, poster and dates.

Scan, 1 operation

  • list_recipe_scansList recipe scansGETAgents: ask firstReturns the scanned images (at most 3) attached to a recipe that was created from a recipe scan, each with its URL in several square sizes, caption and poster.

Use BigOven from Claude Code, Cursor or Codex

Connect BigOven in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its BigOven operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect BigOven

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect BigOven once

    Add your BigOven connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

BigOven integration FAQ

What can you do with the BigOven integration?

LiveContext exposes 17 operations on BigOven, covering recipe, collection, review and all.

Popular integrations

Browse the whole catalog