Metabolic Estimator MCP for AI. Calculates precise energy burn, BMR, and goal timelines.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
The Metabolic Energy Estimator MCP Server handles deterministic calorie and energy math for fitness agents. It calculates Basal Metabolic Rate (BMR) and Total Daily Energy Expenditure (TDEE) using the Mifflin-St Jeor equation, finds exact calories burned from specific activities via a local catalog of 80+ exercises, and projects precise timelines for reaching weight goals based on defined deficits.
What your AI can do
Calculate tdee
Uses weight, height, age, and activity level to calculate your Total Daily Energy Expenditure (TDEE) and Basal Metabolic Rate (BMR).
Estimate calories burned
Calculates precise calories burned using an activity ID, your current weight, and workout duration.
Search activity catalog
Searches a local database for physical activities and returns their official Metabolic Equivalent of Task (MET) values.
The tool calculates your Total Daily Energy Expenditure (TDEE) and Basal Metabolic Rate (BMR) using standard formulas based on age, weight, height, and activity level.
The server searches a local catalog to find the specific Metabolic Equivalent of Task (MET) value for any listed physical activity.
It calculates the exact number of calories burned by running a specific activity, given your weight and how long you worked out.
The server computes the total days or weeks required to hit a target weight based on maintaining a specified daily calorie deficit.
Ask an AI about this
Waiting for input…
Metabolic Energy Estimator: 4 Tools for Fitness Math
Use these four tools to calculate energy expenditure, set baselines (BMR/TDEE), track activity burn rates, and project weight loss timelines.
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 Metabolic Energy Estimator on VinkiusCalculate Tdee
Uses weight, height, age, and activity level to calculate your Total Daily Energy Expenditure (TDEE) and Basal Metabolic Rate (BMR).
Estimate Calories Burned
Calculates precise calories burned using an activity ID, your current weight, and...
Search Activity Catalog
Searches a local database for physical activities and returns their official...
Calculate Weight Loss Projection
Takes a target weight and daily deficit amount to project the exact number of days...
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.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Metabolic Estimator integration is available immediately — no restart needed.
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 Metabolic Energy 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 calorie-burn-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 4 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Figuring out your true calorie burn shouldn't feel like a math exam.
Before this MCP Server, figuring out how many calories an activity burned meant manually looking up formulas, cross-referencing general body weight multipliers, and guessing if the online calculator used MET values or something else entirely. It was slow, manual copy-pasting across three different spreadsheets.
Now, your agent handles it in two calls. First, you get the baseline with `calculate_tdee`. Then, for any activity, calling `search_activity_catalog` and passing that ID to `estimate_calories_burned` gives you the final number instantly. The messy math is gone.
The Metabolic Energy Estimator MCP Server: calculate BMR and TDEE
You used to have to write complex functions that took weight, height, age, gender, and activity multiplier as arguments just to get a baseline number. That logic was fragile and hard to maintain.
Now, the `calculate_tdee` tool handles all that complexity inside its single API call. You send the parameters; you get the accurate TDEE back. It's clean, predictable math.
What your AI can actually do with this
The calculate_tdee tool determines your Total Daily Energy Expenditure (TDEE) and Basal Metabolic Rate (BMR). You input your current weight, height, age, and activity level; it runs those numbers through the established Mifflin-St Jeor equation to give you precise calorie targets. This isn't guesswork—it's deterministic math. The BMR tells you what calories you burn just keeping your organs running; TDEE accounts for everything else you do throughout a day.
When your agent needs to know your baseline energy requirements, it calls this tool. You never send sensitive health data anywhere outside the local process.
The server also provides four key tools that handle every metabolic calculation, so you don't have to trust any random LLM guess. First, if you need background activity data, the search_activity_catalog tool pulls from a local database of physical activities. It gives you the official Metabolic Equivalent of Task (MET) value for anything listed in its 80-plus exercise catalog.
These MET values are critical because they are the industry standard for measuring energy output.
Once you've got that MET value, the estimate_calories_burned tool calculates exactly how many calories you burned during a specific workout. You just feed it an activity ID (which comes from the catalog search), your current weight, and the duration of time you worked out. The result is a precise calorie count for that session.
It’s not rounded; it's calculated based on established metabolic science.
For planning, the calculate_weight_loss_projection tool figures out exactly how long it will take to hit your weight goal. You give it two simple numbers: your target weight and the daily calorie deficit you plan to maintain. The tool runs the math and tells you, in days or weeks, precisely when you’ll reach that number.
This function handles the full timeline projection, making sure you know what's coming up.
Your AI client doesn't guess at energy expenditure; it runs verified calculations every time. It calculates your baseline needs using age, weight, height, and activity level via calculate_tdee. You can find specific MET values for any listed exercise by calling search_activity_catalog. Then, you plug those metrics into the system to get an exact calorie burn rate using estimate_calories_burned, factoring in your body weight and workout length.
Finally, if you're mapping out a plan, the server computes the total time—in days or weeks—required to hit a target weight by maintaining a specified daily deficit amount through calculate_weight_loss_projection. You just plug in the variables and get the definite answer.
019e3873-72a8-7031-b0d7-49d08f847c56 
Here's how it actually works
The bottom line is: it replaces vague estimations with deterministic calculations using established scientific formulas and local data lookups.
First, your AI client calls calculate_tdee with your age, height, weight, and activity level. This establishes your baseline energy requirement.
Next, you use search_activity_catalog to find the correct Activity ID for your exercise (e.g., 'run_moderate'). Then, call estimate_calories_burned using that ID, along with your weight and time.
Finally, if you set a goal, calling calculate_weight_loss_projection takes the target weight and deficit amount to output a precise timeline.
Who is this actually for?
Any developer building fitness, health, or wellness applications needs this. Specifically, the health coach tired of relying on generic calorie calculators, the app developer needing a reliable BMR engine that works offline, and anyone building an agent that needs to give numbers instead of platitudes.
Uses calculate_tdee to set user baselines and estimate_calories_burned to provide accurate workout logging.
Combines all tools—from using search_activity_catalog to calculate activity burn, then running calculate_weight_loss_projection for goal setting—in a multi-step guidance flow.
Integrates the server's deterministic math into product flows that require precise energy balance tracking and progress reporting.
What Changes When You Connect
Eliminates guesswork. Instead of relying on vague LLM estimates for calories burned, use estimate_calories_burned with a specific activity ID to get mathematically exact results based on weight and time.
Establishes accurate baselines instantly. The calculate_tdee tool uses the Mifflin-St Jeor equation to give you your real Basal Metabolic Rate (BMR) and Total Daily Energy Expenditure (TDEE), without sending any sensitive metrics over the wire.
Provides clear goal paths. Use calculate_weight_loss_projection to tell users exactly how many days or weeks they need to maintain a specific caloric deficit to reach their target weight.
Uses deterministic data. The search_activity_catalog function provides reliable MET values for over 80 activities, ensuring your calculations are based on an authoritative source, not general knowledge.
Builds trust with numbers. By providing measurable metrics (like TDEE and BMR), your agent moves from giving advice to delivering verifiable data points.
See it in action
Setting up a new user's baseline plan
A developer needs an agent to welcome a new client. The agent first calls calculate_tdee using the client's age, height, and weight. This establishes the Total Daily Energy Expenditure (TDEE) before any activity logging happens, setting realistic expectations from day one.
Logging a specific workout session
A user finishes an hour of moderate running. The agent first calls search_activity_catalog to get the Activity ID for 'run_moderate'. Then, it passes that ID, along with the user's weight and 60 minutes, into estimate_calories_burned to return a precise calorie count.
Creating a long-term goal roadmap
A client wants to lose 15kg. The agent calculates the total required deficit (77,000 calories) and then uses calculate_weight_loss_projection with an expected daily deficit of 600 calories to output a clear timeline: exactly 22 weeks.
Comparing activity intensity
The agent needs to compare cycling versus swimming. It calls search_activity_catalog for both activities, pulling the MET values. This allows it to explain why one activity burns more calories per minute than another, using deterministic data.
The honest tradeoffs
Asking an LLM for a general estimate
The agent is asked: 'If I lift weights and weigh 80kg, how many calories did I burn?' The AI responds with a vague range like 'maybe 300-500 calories,' which gives no actionable data.
You must break this into steps. First, use calculate_tdee to get the baseline. Then, if you want activity-specific math, use search_activity_catalog and estimate_calories_burned for precision.
Overlooking initial metrics
The user just inputs their target weight (e.g., 80kg) but forgets to give the starting point or daily deficit amount, leading to an error.
Always run calculate_tdee first so the agent knows the baseline energy needs. Then, pass the desired 'daily calorie deficit' into calculate_weight_loss_projection.
Relying on general knowledge for activity
The developer hardcodes MET values or uses simple multiplication (Weight * Time) because they don't want to call a search tool.
Always use search_activity_catalog first. It guarantees you are using the correct, validated MET value needed for accurate calculations in estimate_calories_burned.
When It Fits, When It Doesn't
Use this server if your core requirement is quantitative energy balance: calculating TDEE/BMR, measuring activity burn rates, or projecting timeframes based on a calorie deficit. It's pure math and deterministic data lookups.
Don't use it if you need qualitative advice—like meal ideas, specific macro breakdowns (e.g., 'you need 40% protein'), or dietary suggestions for allergies. For those things, you still need to build out the nutrition planning logic yourself. Remember: this server tells you how many calories are burned; it doesn't tell you what to eat instead.
Questions you might have
How does calculate_weight_loss_projection handle the 7700 calories per kg rule? +
It uses the standard scientific metric of 1kg of body fat equaling approximately 7,700 calories. You just need to provide your target weight and the daily deficit amount.
Do I need search_activity_catalog before running estimate_calories_burned? +
Yes. estimate_calories_burned requires an activityId. You must run search_activity_catalog first to get the specific ID for the activity you want to track.
Is the TDEE calculation safe? +
Yes. The server runs the Mifflin-St Jeor equation locally, meaning your health metrics never leave your environment or go up to a cloud service.
Can I use estimate_calories_burned for weightlifting? +
Yes, as long as 'weightlifting' is in the catalog. You must first run search_activity_catalog to verify its activity ID and MET value for accurate results.
Does running `calculate_tdee` send my health data to a cloud server? +
No, the calculation runs locally on the Vurb engine. Your Basal Metabolic Rate and Total Daily Energy Expenditure never leave your private environment.
What error handling should I expect when using `calculate_weight_loss_projection`? +
If inputs are invalid (like negative weight or deficit), the tool returns a structured error object. Always validate that all provided metrics are positive numbers.
Are there rate limits for calling `estimate_calories_burned`? +
Vinkius manages underlying API throughput, but we recommend implementing exponential backoff logic in your agent client. Check the service dashboard for specific usage caps.
How does `search_activity_catalog` determine which activities are available? +
It queries a deterministic, local index of over 80 physical activities. This means you get immediate access to verified MET values without needing external API calls or network lookup delays.
How does it calculate the calories burned? +
The estimate_calories_burned tool uses the standard metabolic formula: Calories = MET * weight(kg) * time(hours). It pulls the exact MET value from its internal activity catalog.
What formula is used for Basal Metabolic Rate (BMR)? +
The calculate_tdee tool uses the Mifflin-St Jeor equation, which is currently considered the most accurate standard for predicting resting metabolic rate.
How does it project weight loss? +
The calculate_weight_loss_projection tool uses the biological constant that 1kg of body fat equals approximately 7700 calories. It divides the total required deficit by your daily deficit to predict the exact timeline.
We've already built the connector for Metabolic Estimator. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 4 tools are live and waiting.
You're up and running in seconds.
Gemini 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.