Can I query sleep data for a specific date range?

Yes! Use the sleep time series tool to query sleep trends across any date range. You can also inspect a single night in detail with the sleep date tool, including all sleep stages.

What health metrics can I access?

You can access 14 different health metrics: activities, sleep (date & time series), heart rate (date & time series), SpO2, breathing rate, cardio fitness score, body weight, water intake, food logs, device info, and user profile.

Fitbit MCP Server for CrewAI 14 tools — connect in under 2 minutes

Name: Fitbit
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 14 Tools Framework

Connect your CrewAI agents to Fitbit through Vinkius, pass the Edge URL in the `mcps` parameter and every Fitbit 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="Fitbit Specialist",
    goal="Help users interact with Fitbit effectively",
    backstory=(
        "You are an expert at leveraging Fitbit 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 Fitbit "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 14 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 Fitbit MCP Server

Connect your Fitbit account to any AI agent and gain instant access to your comprehensive health and fitness data through natural conversation.

When paired with CrewAI, Fitbit becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Fitbit 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

Activity Tracking — Retrieve daily activity summaries including steps, distance, calories, and active minutes for any date
Sleep Analysis — Access detailed sleep logs with stages (deep, light, REM, awake) for individual nights or time series trends
Heart Rate Monitoring — Query resting heart rate, intraday zones, and historical cardiac trends
SpO2 & Breathing — View blood oxygen saturation levels and breathing rate data
Body Composition — Track weight measurements and cardio fitness scores over time
Nutrition Logs — Access water intake and food logging data for dietary tracking
Device Management — Check connected Fitbit devices and their sync status

The Fitbit MCP Server exposes 14 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 Fitbit to CrewAI via MCP

Follow these steps to integrate the Fitbit 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 14 tools from Fitbit

Why Use CrewAI with the Fitbit MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Fitbit 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

Fitbit + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Fitbit 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 Fitbit, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Fitbit 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 Fitbit against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Fitbit MCP Tools for CrewAI (14)

These 14 tools become available when you connect Fitbit to CrewAI via MCP:

get_activities_date

Returns steps, calories burned, distance walked, active minutes, floors climbed, elevation and sedentary minutes. Date format: YYYY-MM-DD or "today". Get activity summary for a specific date

get_activities_timeseries

Resource paths: "steps", "calories", "distance", "floors", "elevation", "minutesSedentary", "minutesLightlyActive", "minutesFairlyActive", "minutesVeryActive", "activityCalories". Period: 1d, 7d, 30d, 1w, 1m, 3m, 6m, 1y, max or startDate/endDate (YYYY-MM-DD). Detail level: "1min", "5min", "15min", "1day" for intraday data. Get activity time series data over a date range

get_body_weight

Returns weight in kg, BMI, fat percentage and date logged. Date format: YYYY-MM-DD. Get body weight log entries for a specific date

get_breathing_rate

Returns breathing rate in breaths per minute. Available on Fitbit devices with SpO2 sensors. Date format: YYYY-MM-DD. Get breathing rate for a specific date

get_cardio_fitness_score

Returns VO2 Max values and percentile rankings. Date format: YYYY-MM-DD. Get cardio fitness score (VO2 Max) for a date range

get_devices

Returns device version, MAC address, battery level, last sync time and device type. Get all Fitbit devices connected to the user's account

get_foods_date

Returns total calories consumed, macros (carbs, protein, fat), water intake and list of logged foods with meal times. Date format: YYYY-MM-DD or "today". Get food log summary for a specific date

get_heart_date

Returns resting heart rate, heart rate zones (fat burn, cardio, peak, out of range) and calories burned in each zone. Date format: YYYY-MM-DD or "today". Get heart rate summary for a specific date

get_heart_timeseries

Returns resting heart rate and heart rate zones per day. Detail level: "1min", "5min", "15min", "1day" for intraday BPM data. Get heart rate time series data over a date range

get_profile

Returns display name, full name, age, height, weight, gender, locale, timezone, avatar URL and member since date. Get the authenticated user's Fitbit profile

get_sleep_date

Returns sleep start time, duration, minutes asleep, minutes awake, minutes in each sleep stage (light, deep, REM, awake), efficiency score and number of awakenings. Date format: YYYY-MM-DD or "today". Get sleep log for a specific date

get_sleep_timeseries

Returns daily sleep summaries with start time, duration, minutes asleep, efficiency and sleep stages. Date range format: startDate/endDate (YYYY-MM-DD). Get sleep log over a date range

get_spo2

Returns average SpO2 percentage and min/max values. Available on Fitbit devices with SpO2 sensors. Date format: YYYY-MM-DD. Get blood oxygen saturation (SpO2) for a specific date

get_water

Returns water consumption in milliliters and timestamps. Date format: YYYY-MM-DD. Get water intake log for a specific date

Example Prompts for Fitbit in CrewAI

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

"How did I sleep last night?"

"Show my heart rate trends for the past week."

Troubleshooting Fitbit MCP Server with CrewAI

Common issues when connecting Fitbit 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.

Fitbit + CrewAI FAQ

Common questions about integrating Fitbit 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.