4,000+ servers built on vurb.ts
Vinkius

Metabolic Energy Estimator MCP Server for CrewAIGive CrewAI instant access to 4 tools to Calculate Tdee, Calculate Weight Loss Projection, Estimate Calories Burned, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Metabolic Energy Estimator through Vinkius, pass the Edge URL in the `mcps` parameter and every Metabolic Energy Estimator tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Metabolic Energy Estimator MCP Server for CrewAI is a standout in the Data Analytics category — giving your AI agent 4 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Metabolic Energy Estimator Specialist",
    goal="Help users interact with Metabolic Energy Estimator effectively",
    backstory=(
        "You are an expert at leveraging Metabolic Energy Estimator tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Metabolic Energy Estimator "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 4 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Metabolic Energy Estimator
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Metabolic Energy Estimator MCP Server

Autonomous health and fitness agents demand uncompromising metabolic accuracy. When standard LLMs attempt to estimate calories burned for a specific activity, they guess wildly. The Metabolic Energy Estimator MCP empowers your AI Agent by delegating this logic to a deterministic engine utilizing scientifically validated MET (Metabolic Equivalent of Task) values.

When paired with CrewAI, Metabolic Energy Estimator becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Metabolic Energy Estimator tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

Core Capabilities

  • Agentic Calorie Estimation: Search a native, offline catalog of over 80 specific physical activities and calculate exact calories burned based on the user's exact weight and duration.
  • TDEE & BMR Engine: Implements the rigorous Mifflin-St Jeor equation to establish the user's Basal Metabolic Rate and Total Daily Energy Expenditure without sending health metrics to the cloud.
  • Weight Loss Projection: Compute the exact number of days and weeks required to hit a target weight given a precise daily caloric deficit, complete with safety warnings.

The Metabolic Energy Estimator MCP Server exposes 4 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 4 Metabolic Energy Estimator tools available for CrewAI

When CrewAI connects to Metabolic Energy Estimator through Vinkius, your AI agent gets direct access to every tool listed below — spanning metabolic-calculation, fitness-tracking, tdee, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

calculate

Calculate tdee on Metabolic Energy Estimator

Calculates Total Daily Energy Expenditure (TDEE) and Basal Metabolic Rate (BMR) using the Mifflin-St Jeor equation

calculate

Calculate weight loss projection on Metabolic Energy Estimator

1kg of fat = 7700 calories. Projects how many days and weeks it will take to reach a target weight based on a daily calorie deficit

estimate

Estimate calories burned on Metabolic Energy Estimator

You MUST provide an activityId found via search_activity_catalog. Calculates exactly how many calories are burned doing a specific physical activity based on weight and time

search

Search activity catalog on Metabolic Energy Estimator

Searches the deterministic local catalog for activities and their exact MET values

Connect Metabolic Energy Estimator to CrewAI via MCP

Follow these steps to wire Metabolic Energy Estimator into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 4 tools from Metabolic Energy Estimator

Why Use CrewAI with the Metabolic Energy Estimator MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Metabolic Energy Estimator through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Metabolic Energy Estimator + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Metabolic Energy Estimator MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Metabolic Energy Estimator for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Metabolic Energy Estimator, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Metabolic Energy Estimator tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Metabolic Energy Estimator against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Metabolic Energy Estimator in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Metabolic Energy Estimator immediately.

01

"I weigh 80kg and ran moderately for 45 minutes. How many calories did I burn?"

02

"I am a 30-year-old male, 180cm, 85kg, with a sedentary lifestyle. What is my TDEE?"

03

"I weigh 90kg and want to reach 80kg with a 500 calorie daily deficit. How long will it take?"

Troubleshooting Metabolic Energy Estimator MCP Server with CrewAI

Common issues when connecting Metabolic Energy Estimator to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Metabolic Energy Estimator + CrewAI FAQ

Common questions about integrating Metabolic Energy Estimator MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Explore More MCP Servers

View all →