BigOven MCP for AI. Search recipes and plan meals by ingredients.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
BigOven connects your AI agent directly to a database of over a million recipes. Search by ingredient, find seasonal collections, or pull full nutritional details for meal planning right from your chat interface.
What your AI can do
Get collection
Fetches the full details and recipes belonging to a specific themed collection.
Get recipe photos
Pulls visual guides and photos associated with a specific recipe ID.
Get recipe reviews
Gathers user feedback, ratings, and comments for a specified dish.
Find dishes when you know the type of food or a main ingredient.
Get recipes that use specific combination of ingredients, like 'salmon' and 'sweet potato'.
Pull full recipe information, including step-by-step instructions, from a known dish.
Check user reviews and star ratings for dishes to vet the quality before using them.
Browse curated or seasonal collections of recipes, like 'Holiday Baking' or 'Summer Grilling'.
Ask an AI about this
Waiting for input…
BigOven: 8 Available Tools
These tools let you search for dishes by keyword or ingredients, retrieve full recipe details, manage collections, and read community reviews.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using BigOven on VinkiusGet Collection
Fetches the full details and recipes belonging to a specific themed collection.
Get Recipe Photos
Pulls visual guides and photos associated with a specific recipe ID.
Get Recipe Reviews
Gathers user feedback, ratings, and comments for a specified dish.
Get Recipe
Retrieves all instructions, ingredients, and metadata for one particular recipe.
List Categories
Lists all valid recipe categories available to filter your search results.
List Collections
Shows the names of seasonal or curated groupings of recipes.
Search By Ingredient
Searches for recipes that must include specific ingredient keywords.
Search Recipes
Performs a general search for dishes based on title or keyword input.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with BigOven, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by BigOven. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 8 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Figuring out what you can cook with random stuff feels like detective work.
Right now, if you're staring at half a bag of lentils and some oddly colored peppers, finding a recipe means opening the site, manually typing 'lentil', then adding 'pepper,' hoping a search bar catches it. Then you have to scroll through pages until you find one that looks okay enough.
With this MCP, you tell your agent what you've got. It runs `search_by_ingredient` and delivers precise matches instantly. You get the recipe details immediately, no scrolling or guesswork required.
Get Recipe Details with `get_recipe`. The instructions are ready to copy.
The old way meant finding a basic result and then having to click on another page just to view the full list of steps, ingredients, and measurements. It was a lot of unnecessary clicks and context switching.
Now, you call `get_recipe` through your agent, and all the necessary data arrives in one block. You copy the instructions directly into your document without ever leaving your chat window.
What your AI can actually do with this
Need recipe ideas fast? This MCP lets you talk to BigOven and get immediate results without opening a browser tab. You can ask your agent to search for dishes using just keywords, or narrow things down by listing available ingredients first. Want to plan meals around what's left in the pantry? Just name two or three items, and the system finds matching recipes.
The data goes further than just instructions; you can pull full nutritional breakdowns and read community reviews before committing to a recipe. Because this MCP is hosted on Vinkius, you connect once from any compatible client and gain access to all these culinary tools in one place.
019d755c-0bee-736d-8ae5-9328d9fd4de7 Here's how it actually works
The bottom line is you talk to it like talking to a friend, and the MCP handles all the database lookups in the background.
Subscribe to this MCP and provide your BigOven API key.
Your agent sends a natural language request (e.g., 'Find Italian pasta recipes').
The system executes the appropriate tool, returning detailed recipe data directly back to your chat session.
Who is this actually for?
Food bloggers who need constant recipe ideas. Meal planners stuck staring at random leftovers. Health coaches needing reliable nutritional data for clients.
Needs to quickly research ingredient combinations and pull full instructions without leaving their writing editor.
Must retrieve accurate nutritional data for recipes to advise clients on dietary restrictions or weight goals.
Wakes up realizing they have chicken and rice, and needs recipe variations instantly based on those leftovers.
What Changes When You Connect
You don't have to guess what recipe exists. By using list_categories or list_collections, you can see all the thematic options available in one go.
Planning around leftovers just got simple. Instead of manual searching, use search_by_ingredient and provide your agent with two or three random items from the fridge.
Before publishing a recipe, check its reputation using get_recipe_reviews. This gives you real-world user feedback that helps shape the final instructions.
Need visuals? After finding a dish via search_recipes, use get_recipe_photos to pull accompanying images so your agent can format them into an article.
You get complete details, not just summaries. The get_recipe tool pulls out everything—ingredients, steps, and even nutritional data—in one shot.
See it in action
Designing a Weekly Menu
A user asks their agent to plan meals for a family of four. The agent runs search_by_ingredient using the ingredients they have (chicken, broccoli, rice). It pulls three matching recipes and provides links to check the nutritional data via get_recipe.
Writing a Food Blog Post
A food blogger wants to write about autumn desserts. They first run list_collections to find 'Fall Baking'. Then, they use search_recipes on the results and pull multiple recipes, gathering photos using get_recipe_photos for the accompanying article.
Comparing Recipe Versions
A user wants to know if a recipe is reliable. They find 'Classic Lasagna' via search_recipes, then they use get_recipe_reviews immediately to see what other people say about the crust or sauce.
Quick Ingredient Check
A chef needs a recipe for dinner using only pantry staples. They run list_categories first, select 'Italian', and then use search_recipes to narrow it down by keyword like 'pasta'.
The honest tradeoffs
Searching too vaguely
Typing into the agent: 'Give me a good dinner recipe.' This is too broad, and the system might return irrelevant or non-specific results.
Don't just ask for dinner. Use list_categories to narrow it down first (e.g., 'Dinner -> Mediterranean'). Then use search_recipes with a keyword like 'chicken'.
Forgetting the full details
The agent only gives the recipe name and star rating, forcing you to jump back into the app for instructions.
Always follow up by using get_recipe on the specific ID provided. That pulls all ingredients, steps, and nutritional info immediately.
Assuming a search endpoint exists
Telling your agent: 'Find recipes with high protein.' The general search might miss this constraint.
The best way to constrain results is using search_by_ingredient and listing the required proteins, or asking the agent to run get_recipe after you've selected a recipe.
When It Fits, When It Doesn't
Use this MCP if your main goal is discovery. Specifically, if you need to filter recipes by ingredients on hand (search_by_ingredient), check community ratings (get_recipe_reviews), or explore thematic groups (list_collections). Don't use it if you are trying to build a completely custom recipe from scratch without existing data; for that, you'd need raw API access. If your goal is simply to browse general categories and don't have specific ingredients in mind, start by running list_categories to see the available filters first. It provides the necessary structure before attempting a search.
Questions you might have
How do I find a recipe for my specific leftover ingredients using search_by_ingredient? +
Use search_by_ingredient and list all the items you have. The system finds matching recipes that incorporate every ingredient you listed.
What is the difference between list_collections and get_collection? +
list_collections shows you a menu of available themes (e.g., 'Mexican Fiesta'). get_collection takes one of those names and pulls all the recipes inside that theme.
Can I check reviews for a recipe using get_recipe_reviews? +
Yes, just provide the recipe ID. The system pulls common user comments and ratings so you know if the dish is worth trying before cooking it.
Do I need to use search_recipes for everything? +
No. While search_recipes works for general keywords, using list_collections or search_by_ingredient will give you more focused and accurate results.
When should I use `get_recipe` if I already know a recipe's ID? +
It returns comprehensive data for that single dish, including ingredients, instructions, and nutritional facts. Think of it as your full source file when you need every detail about one specific meal.
Before searching, do I need to run `list_categories` to see all valid filters? +
Yes, running list_categories shows you every recognized recipe type. Use this list first so your AI agent can filter search results accurately and quickly.
If I need visuals for a dish, how does `get_recipe_photos` help me plan a meal? +
This tool fetches visual guides and photos linked to the recipe ID. It lets your AI client build out a complete plan that includes media, which is great for presentation or printing.
If my agent makes many calls, are there rate limits when using this MCP? +
Vinkius manages general usage throttling for the entire catalog. If you hit a limit, watch the API error codes; they tell you exactly when your agent needs to pause and try again later.
Can I search for recipes based on ingredients I have in my fridge? +
Yes! Use the search_by_ingredient tool and provide the ingredients you have (e.g., 'chicken, broccoli'). The agent will return recipes you can make.
How do I get the step-by-step instructions for a recipe? +
First, find the Recipe ID using the search tools. Then, ask the agent to get_recipe with that ID. It will retrieve the full ingredient list and step-by-step instructions.
Does the integration allow me to add recipes to a grocery list? +
Currently, the toolset is focused on public discovery and searching (Read-Only). Managing personal grocery lists requires user-specific OAuth which is managed directly on the BigOven app.
We've already built the connector for BigOven. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 8 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.