Nutritional Estimator MCP for AI. Calculate nutrition from ingredient weights instantly.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Nutritional Estimator calculates total and per-serving macro and calorie counts for any recipe. It takes ingredient weights and uses standardized nutrient data to give you precise breakdowns of protein, fat, carbs, and fiber, whether you're developing a new menu or balancing macros for a client.
What your AI can do
Compute recipe nutrition
Calculates the total nutrition and per-serving breakdown for an entire recipe based on provided weights.
Get ingredient details
Retrieves the specific nutritional profile, including calories and macros, for a single listed ingredient.
Search ingredients
Searches the nutrient database by name or keyword to return a list of matching ingredients available in the registry.
Search the nutrient database by name or keyword to find potential components for a recipe.
Pull up the full nutritional profile, including macros and calories, for any specific item in the registry.
Perform complex calculations to determine the combined macro and calorie content of a weighted recipe batch or portion.
Ask an AI about this
Waiting for input…
Nutritional Estimator: 3 Tools
These three tools allow you to search for food components, check their specific nutrient profiles, and calculate the total nutrition for any recipe batch.
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 Nutritional Estimator on VinkiusCompute Recipe Nutrition
Calculates the total nutrition and per-serving breakdown for an entire recipe based on provided weights.
Get Ingredient Details
Retrieves the specific nutritional profile, including calories and macros, for a...
Search Ingredients
Searches the nutrient database by name or keyword to return a list of matching...
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 Nutritional Estimator, 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 Nutritional Estimator. 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 3 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually tracking nutrition from recipes is a nightmare of spreadsheets.
Today, creating a comprehensive recipe sheet means opening nutrient databases, searching by ingredient name, copy-pasting the relevant calorie and macro data into a spreadsheet, and then manually writing formulas to scale the totals. It's slow, it's tedious, and honestly, you always worry about accidentally mixing up a cell reference.
With this MCP, your agent handles that entire process in one go. Give it the ingredient list and weights, and it gives you the clean, aggregated data you need for marketing copy or client reports. You get accuracy without the spreadsheet headaches.
The Nutritional Estimator MCP provides recipe calculation.
You eliminate the need to jump between tabs and use multiple formulas just to calculate total protein across a dozen ingredients. The system handles the weighting and summation logic for you, whether it's a full batch or a single serving size.
The difference is simple: you stop doing math and start reviewing results. You get actionable nutritional reports instantly.
What your AI can actually do with this
Need to know the exact nutrition breakdown of a complex dish? This MCP lets your agent transform raw ingredients into usable nutritional reports. You provide weights—say, 200 grams of chicken breast and 150 grams of rice—and it handles all the math. Instead of cross-referencing multiple databases or wrestling with spreadsheets, the tool aggregates total calories, proteins, fats, carbs, and fiber for a full batch or for single servings.
This works because it taps into a local database of nutrient densities, keeping your data reliable. If you're building an application that needs to process food science data, Vinkius makes this MCP available right in your workflow so your AI client can access the calculation power instantly.
019eef7d-583b-735c-9d50-91bfd0310183 Here's how it actually works
The bottom line is that it turns disparate pieces of data (ingredients) into one clean calculation (the final nutrition panel).
First, you use your agent to find items in the registry using search_ingredients if you don't know the exact ID.
Next, you pull specific nutritional data for those ingredients using get_ingredient_details to confirm nutrient profiles and standards.
Finally, you feed all the weights and details into compute_recipe_nutrition to get a single report with total and per-serving counts.
Who is this actually for?
Dietitians, culinary developers, and food product manufacturers. If your job involves converting recipes or ingredient lists into quantifiable nutritional facts, this MCP saves you hours of manual spreadsheet work.
Needs to quickly calculate the full macro profile for a client's daily meal plan using various food sources.
Must estimate the nutritional output of a prototype recipe mix before sending it to quality control testing.
Calculates serving sizes and total caloric content for a restaurant's new seasonal menu items.
What Changes When You Connect
Stop manually cross-referencing nutrient databases. Using get_ingredient_details lets your agent pull the exact macro and calorie data for any item, ensuring accuracy right out of the gate.
Get a complete picture of a recipe's nutritional content without leaving your workflow. The tool handles complex scaling calculations via compute_recipe_nutrition, giving you both total and per-serving counts.
If you just need to know if an ingredient exists or what it’s called, use search_ingredients. This prevents unnecessary data calls when you're simply listing components for a menu.
Eliminate spreadsheet errors. By letting the MCP handle the math using weights and standardized densities, you get reliable totals every time.
Speed up product development. You can test multiple recipe variations in minutes, getting immediate feedback on protein, fat, and carb balance.
See it in action
Developing a new macro-friendly meal plan
A dietitian needs to build a 500-calorie lunch for a client using chicken, quinoa, and mixed greens. They ask their agent, which then uses search_ingredients first. It gathers the necessary details via get_ingredient_details, finally running compute_recipe_nutrition to give them the precise macro totals needed.
Scaling a corporate cafeteria menu item
A food developer has a recipe that serves 10 people, but needs to adjust it for single-serving meal kits. They input all weights into compute_recipe_nutrition, and the tool immediately provides the precise per-serving nutrient breakdown.
Checking nutritional feasibility
A client says they can't eat anything with high fiber content. The agent uses search_ingredients to pull a list of potential replacement items, then runs get_ingredient_details on those matches to filter out high-fiber options before the chef even starts cooking.
The honest tradeoffs
Using details when you just need names
A user tries to calculate nutrition by running get_ingredient_details for a list of 20 ingredients, even though they only needed to know if the items were present in the system.
If your goal is simple discovery or checking availability, always start with search_ingredients. This tool keeps things quick and prevents you from pulling unnecessary nutritional data.
Skipping the calculation step
A developer pulls nutrition details for several ingredients but forgets to run a final computation function. They end up manually adding calories, which is prone to arithmetic mistakes.
After gathering all ingredient data using get_ingredient_details, you must pass everything into compute_recipe_nutrition to get an accurate, total recipe count.
When It Fits, When It Doesn't
Use this MCP if your task requires quantifying food or drink recipes based on specific component weights. The core workflow is: find the ingredient (search) -> check its data (details) -> calculate the final number (compute). Don't use it if you just need to know a general nutritional fact about one item; in that case, simply checking the details via get_ingredient_details is enough. You only run the full calculation when you have multiple components and specific weights for every single one.
Questions you might have
How does the nutritional calculation work? +
The system uses a 100g reference standard. It scales the nutrient values of each ingredient by its weight in grams relative to that 100g base, then sums all contributions for the total recipe and divides by the number of servings for per-portion data.
Can I search for ingredients by partial names? +
Yes, the search_ingredients tool performs a case-insensitive search that matches any part of the ingredient name in the local database.
What happens if an ingredient ID is not found? +
If you provide an invalid or non-existent ID to get_ingredient_details or compute_recipe_nutrition, the tool will return a failure status with a descriptive error message.
When using `compute_recipe_nutrition`, must I provide weights in grams? +
Yes, you must provide ingredient masses by weight. The MCP requires all input measurements to be standardized in grams (g) because the underlying nutrient database uses 100g as its base unit for density calculations.
What specific nutritional data does `get_ingredient_details` return? +
It returns a full profile of macronutrients, including calories, protein grams, fat grams, carbohydrates grams, and fiber grams. This gives you the complete picture needed to plan meals or check dietary requirements.
Can `search_ingredients` filter results by specific food categories? +
The search function allows filtering beyond just keywords. You can narrow down your ingredient list by specifying category types, ensuring you only retrieve items like 'Grains' or 'Dairy'.
How does `compute_recipe_nutrition` handle the serving size calculation? +
The tool takes a total yield weight and the desired number of servings. It then accurately divides the calculated total nutrition, providing precise per-serving metrics for you to use.
Are there any usage limits or rate restrictions when calling `compute_recipe_nutrition`? +
The platform manages typical rate limiting automatically to ensure stable performance. If you exceed a high volume of complex calculations rapidly, your agent will receive an appropriate request limit error.
We've already built the connector for Nutritional Estimator. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 3 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.