TheMealDB Extended MCP for AI. Find any recipe by ingredient, area, or category.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
TheMealDB Extended connects your AI agent to a massive global recipe database. You can find meal ideas by ingredients you have on hand, filter dishes by country or cuisine type, and retrieve full cooking instructions using unique IDs.
It's basically an instant sous-chef for your prompts.
What AI agents can do with TheMealDB Automation
Filter by area
Narrows down recipes by selecting a specific country or geographical region.
Filter by category
Limits the meal results to a selected food group, like 'Dessert' or 'Seafood'.
Filter by ingredient
Finds recipes that contain one or more specific ingredients you list.
List all available meal categories or filter recipes based on a specific country or region.
Search for recipes using one or more main components you have in your pantry, bypassing the need to know the recipe name.
Look up a single meal's complete instructions and ingredient list using its unique Meal ID.
List all available categories, areas, or ingredients to understand what filters your agent can use next.
Ask an AI about this
Waiting for input…
What AI agents can do with TheMealDB Extended MCP Server: 13 Tools for Culinary Retrieval
Use these tools to perform deep searches against the meal database. Filter results by area, category, ingredients, and find specific recipes by name or ID.
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 TheMealDB on VinkiusFilter By Area
Narrows down recipes by selecting a specific country or geographical region.
Filter By Category
Limits the meal results to a selected food group, like 'Dessert' or 'Seafood'.
Filter By Ingredient
Finds recipes that contain one or more specific ingredients you list.
Get Latest Meals
Retrieves a list of the most recently added dishes in the database (Premium V2...
Get Meal By Id
Looks up and returns all detailed information for one meal using its unique ID...
Get Random Meal
Returns the full details of a single, random recipe from the entire database.
Get Random Meals Selection
Retrieves a selection of 10 unique random meals (Premium V2 required).
List All Categories
Returns a full list of all recognized meal categories and their descriptions.
List Areas
Provides a simple, browsable list of countries or major geographic regions.
List Categories
Lists all available meal categories for easy browsing and filtering.
List Ingredients
Provides a simple, browsable list of common ingredients used in recipes.
List Meals By First Letter
Lists all available meals that start with a specific letter (A-Z).
Search Meals By Name
Searches the database for recipes matching a full or partial name string.
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 TheMealDB, 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 TheMealDB. 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
Built on the Model Context Protocol (MCP) for 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 13 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Staring at a blank fridge and scrolling through recipe blogs., Solved with Vinkius AI Gateway
Right now, you pull out your phone, open three different tabs—Pinterest, Google Search, and maybe an old cookbook PDF. You copy-paste ingredients into one search bar, then manually filter results by region until you find something that works. It takes five minutes of clicking through irrelevant dishes.
With TheMealDB Extended MCP Server, you just tell your agent: 'I have chicken breast and pasta.' Your agent runs `filter_by_ingredient` against the entire database and hands you three actionable recipes instantly. No more manual cross-referencing.
TheMealDB Extended MCP Server: Find Recipes by Ingredient, Area & Category
Before this server, finding dishes that matched a specific global cuisine *and* an ingredient meant multiple steps of searching and filtering across different platforms. You had to assume the database was structured correctly.
Now, your agent manages the complexity. It takes 'Mexican' (via `filter_by_area`) and combines it with 'Beans' (via `filter_by_ingredient`). The result is precise, verifiable data that gets you cooking immediately.
What your AI can actually do with this
Listen up. When you connect your AI agent to TheMealDB Extended, you're hooking it up to a massive recipe database—like having an instant sous-chef right in your chat window. This isn't just another search box; the server gives your agent specific tools so it can talk directly to the food data.
You don't ask one big question and hope for the best; you run precise commands, making sure you get exactly what you need.
Finding Meals by Geography and Type
Need an idea based on where you are or what kind of meal it is? The server lets your agent narrow things down fast. You can use list_areas to pull a simple list of every country or big region in the database, then filter_by_area to restrict results—say, only dishes from Italy.
If geography isn't enough, you can check out what kind of food groups are available by calling list_categories, and then use filter_by_category to limit your search to something specific like 'Seafood' or 'Dessert'. You also don't have to guess; the tool list_all_categories gives you a full rundown of every single meal category they track.
Need to know what ingredients are even in there? Use list_ingredients—it spits out a browsable list of common pantry items.
Filtering Dishes by Ingredients
This is the killer feature: Forget trying to remember a recipe name. You just tell your agent which main components you've got lying around, and it finds recipes using those ingredients. The filter_by_ingredient tool searches for meals based on one or more specific items you list. It bypasses the need for knowing any recipe names at all.
Retrieving Full Recipe Details
If your agent finds a meal it likes, getting the details is simple. You can use get_meal_by_id to look up every single piece of info—the full ingredient list, measurements, and step-by-step instructions—using that unique Meal ID number. Need something quick? Use get_random_meal for one dish or get_random_meals_selection if you want a set of ten totally random ideas.
If you're just testing the waters, your agent can always call get_latest_meals (you gotta have Premium V2 for that one) to see what dishes were added most recently.
Browsing the Database Structure and Searching Names
The server gives you a ton of ways to explore. If you want to search by name, use search_meals_by_name to check against recipes matching either all or part of a string you give it. For more targeted browsing, your agent can call list_meals_by_first_letter, which lists every meal available that starts with a specific letter (A through Z).
You also have tools like get_random_meal and get_random_meals_selection so you don't get stuck—you always got options.
Basically, whether you wanna find dishes from Vietnam using chicken and rice, or you just wanna see what random dessert is available today, your agent has the tools to make it happen. It’s a complete system that lets you drill down into any kind of culinary data.
019e5d5f-271c-7270-9da7-c4267d05ec24 Here's how it actually works
The bottom line is you’re chaining specialized API calls together: list options -> filter parameters -> retrieve data.
First, tell the agent what you want to narrow down. You'll need to run a listing tool like list_categories to see available options.
Next, use one of the filtering tools—for example, if you know it's a pasta dish and from Italy, you'd call filter_by_category then filter_by_area.
Finally, pass the results or specific filters into a retrieval tool like get_meal_by_id to get the full recipe details.
Who is this actually for?
Anyone who gets frustrated when a search engine gives them millions of results and they just need one good idea. This is for the content creator juggling 10 blog posts, the developer building a recipe app feature, or the home cook standing in front of a fridge full of random ingredients.
Needs to gather inspiration and data for weekly content. Uses list_categories and search_meals_by_name to populate blog posts, then uses get_meal_by_id to grab specific instructions.
Builds food-related features. Uses the listing tools (list_ingredients, list_areas) to build structured filter UIs, then calls filter_by_ingredient to test data retrieval.
Needs to understand global cuisine. Uses list_areas and filter_by_area repeatedly to build a database of regional dishes.
What Changes When You Connect
Stop guessing what to cook. Use list_ingredients and then pass that list into filter_by_ingredient. Your agent immediately gives you a curated set of dishes using only what's in your pantry.
Never get stuck on cuisine type again. Run list_categories first, then use filter_by_category to narrow down the results—whether you’re looking for 'Pasta' or 'Vegan'.
Need a quick idea? Call get_random_meal. You instantly get a full recipe, measurements included, without having to search anything.
If you only have an ID number (maybe from a previous search), use get_meal_by_id. It bypasses all the searching and pulls up the entire dish record directly.
Build robust client logic. The listing tools (list_areas, list_categories) let your agent build filters programmatically, giving you complete control over data filtering.
See it in action
The Fridge Raid
A user opens the chat with: 'I have chicken, rice, and soy sauce. What can I make?' The agent calls list_ingredients to confirm 'chicken' is valid, then runs filter_by_ingredient using those three items. It returns a list of possible recipes.
The Global Blogger
A content creator needs 10 ideas for an article on Asian cuisine. They ask the agent to use list_areas and then run filter_by_area specifically for 'Japanese'. The agent returns a list of dishes they can write about.
The Targeted Search
A developer needs all desserts from Italy. They call list_categories to confirm 'Dessert' is valid, then run filter_by_category, and finally refine that result by calling filter_by_area for 'Italy'.
The Quick Reference
A user knows a recipe ID (52773) but can't remember the name. They just pass the ID to the agent, which executes get_meal_by_id and prints out the full instructions instantly.
The honest tradeoffs
Searching for everything at once
Asking the agent: 'Find me a delicious Japanese dessert made with chicken.' The system will fail because no single tool handles all those parameters.
You have to break it down. First, run filter_by_area for 'Japan'. Then, filter that result by filter_by_category using 'Dessert'. Finally, if you need the ingredient confirmation, use filter_by_ingredient.
Assuming a simple search function exists
Thinking that just typing 'Italian pasta' into the chat is enough. The agent can’t guess which tool to run.
Always start by listing parameters. Run list_categories and confirm 'Pasta'. Then, use filter_by_category with the correct term.
Overlooking the core data structure
Trying to search for a recipe without knowing if it exists in the database. You'll get zero results and think the tool is broken.
Always try search_meals_by_name first, or better yet, use list_areas to confirm which regions are available before filtering.
When It Fits, When It Doesn't
Use this server if your workflow requires deep data retrieval based on multiple, distinct criteria (area AND category AND ingredient). Don't use it if you just need a general 'recipe idea'; those usually come from simpler keyword search. If you only need to find dishes by name, search_meals_by_name is enough. But if the user says, 'Show me things that are both Italian and contain tomatoes,' you must chain calls: use filter_by_area('Italy') followed by filter_by_ingredient(['tomato']). This server is for expert-level data filtering, not casual browsing.
Questions you might have
How do I find recipes using the TheMealDB Extended MCP Server? +
You start by listing what's available. Run list_categories to see if 'Dessert' is a valid filter, then use filter_by_category('Dessert').
Can TheMealDB Extended MCP Server search by multiple ingredients? +
Yes, the filter_by_ingredient tool accepts comma-separated values for V2 premium users. You just list them out: 'chicken, rice, soy sauce'.
What is the difference between `get_random_meal` and `get_random_meals_selection`? +
get_random_meal gives you one full recipe. get_random_meals_selection (Premium V2) gives you a curated list of 10 random recipes to choose from.
How do I find all possible filter options for TheMealDB Extended MCP Server? +
You run the listing tools: list_areas shows countries, while list_categories shows meal types. They give you the required inputs for filtering.
What key do I need to successfully use `get_latest_meals` with TheMealDB Extended MCP Server? +
You require a premium V2 API key. If you try to run this tool without the correct credentials, the server will reject the request and return an authentication error. Always check your subscription status for premium features.
If I use `get_meal_by_id` in TheMealDB Extended MCP Server but provide a meal ID that doesn't exist, what happens? +
The tool handles invalid inputs gracefully. Instead of crashing, the server will return an error message or an empty set of results, letting your agent know the requested ID is not found in the database.
When using `filter_by_ingredient` with TheMealDB Extended MCP Server, how should I structure a list of multiple ingredients? +
For premium V2 users, you must separate multiple ingredients by commas. For example, use 'chicken, tomato, oregano' instead of listing them one after the other.
How can TheMealDB Extended MCP Server help me explore all global cuisine types? +
You first call list_areas to get a comprehensive list of regions and countries. Then, you pass those specific areas into the filter_by_area tool for targeted results.
How do I get the full cooking instructions for a specific meal? +
Use the get_meal_by_id tool with the unique Meal ID. The agent will return the full recipe, including step-by-step instructions and a complete list of ingredients with measurements.
Can I search for recipes based on what I have in my fridge? +
Yes! You can use the filter_by_ingredient tool to find meals that feature a specific main ingredient. For Premium V2 users, you can even provide a comma-separated list of multiple ingredients.
What is the difference between the free and premium API access? +
The free tier (API key '1') allows standard searching and filtering. Premium V2 access enables advanced tools like get_latest_meals, get_random_meals_selection (10 at once), and multi-ingredient filtering.
We've already built the connector for TheMealDB Extended. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 13 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.