How do I filter for specific measurements like Body Fat or Blood Pressure?

Use the `meastype` parameter with the `get_measurements` tool. Common types: 1 (Weight), 4 (Height), 8 (Fat Mass), 9 (Diastolic BP), 10 (Systolic BP), 11 (Heart Pulse), 71 (Body Temperature).

What is the difference between sleep summary and sleep details?

`get_sleep_summary` returns one overall score and total duration per night. `get_sleep_details` returns high-frequency intraday data, detailing exactly what time you entered REM, deep sleep, or woke up throughout the night.

Can I receive real-time notifications when I step on the scale?

Yes, use the `subscribe_notifications` tool with an `appli` ID of 1 (Weight). Withings will then send a POST webhook to the callback URL you specify the moment a new weight measurement is synced.

Withings MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Withings
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Withings Specialist",
    goal="Help users interact with Withings effectively",
    backstory=(
        "You are an expert at leveraging Withings 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 Withings "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 Withings MCP Server

Connect your Withings account to any AI agent to unlock deep insights into your health, wellness, and fitness data collected by Withings smart scales, watches, and medical devices.

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

What you can do

Medical Measurements — Track weight, body fat %, systolic/diastolic blood pressure, and heart pulse trends over time
Sleep Analytics — Access daily sleep scores, deep/light/REM sleep stage durations, and sleep efficiency metrics
Activity Tracking — Analyze daily step counts, active calories burned, and precise intraday activity levels
Workout Logging — Review distinct workout sessions (running, swimming, cycling) with categorizations and duration
Device Management — Check the battery status and connection status of your Withings hardware fleet
Real-time Notifications — Configure webhooks to receive instant alerts when new measurements (like a morning weigh-in) are recorded

The Withings MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Withings to CrewAI via MCP

Follow these steps to integrate the Withings MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Withings

Why Use CrewAI with the Withings MCP Server

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

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

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

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

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

Withings + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Withings MCP Server delivers measurable value.

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

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

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

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

Withings MCP Tools for CrewAI (10)

These 10 tools become available when you connect Withings to CrewAI via MCP:

get_activity

Get daily activity summaries (steps, calories)

get_heart_rate

Get specific heart rate measurements

get_intraday_activity

Get high-frequency intraday activity data

get_measurements

Use meastype to filter (1=Weight, 4=Height, 9=Diastolic BP, 10=Systolic BP, 11=Heart Pulse, 71=Body Temp). Dates should be YYYY-MM-DD. Get physiological measurements (weight, blood pressure, etc)

get_sleep_details

Get detailed sleep data (stages and states)

get_sleep_summary

Get daily sleep summaries

get_user_devices

List user's Withings devices

get_user_goals

Get user health and fitness goals

get_workouts

g., running, swimming, cycling) with their specific duration, calorie burn, distance, and activity category. Get recorded workouts and exercises

subscribe_notifications

g. immediately after a user steps on a scale). Appli codes: 1(weight), 4(BP), 16(activity), 44(sleep). Subscribe to Withings webhook notifications

Example Prompts for Withings in CrewAI

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

"Retrieve my weight and body fat measurements for the last 30 days."

"What was my sleep score and total sleep time last night?"

"Analyze my activity levels over the weekend. Did I hit my step goals?"

Troubleshooting Withings MCP Server with CrewAI

Common issues when connecting Withings to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Withings + CrewAI FAQ

Common questions about integrating Withings MCP Server with CrewAI.

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.

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.

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.

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.

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.