Fitbit

🚀 Fitbit Model Context Protocol (MCP) Server

This project implements a server compliant with the Model Context Protocol (MCP), serving as a bridge between large language models (such as Claude) and the Fitbit API.

It enables LLMs to request and retrieve health and fitness data from users' Fitbit accounts and interact through defined tools.

✨ Features

• Fitbit API Integration: Securely connect to the Fitbit API using OAuth 2.0.
• MCP Compatibility: Provide Fitbit data through tools compliant with the Model Context Protocol.
• Scalability: Designed to easily add support for more Fitbit API endpoints.

Supported Endpoints

• Weight:
  • get_weight: Retrieve raw weight data for a specified time period (1d, 7d, 30d, 3m, 6m, 1y), ending today. Requires a period parameter.
• Sleep:
  • get_sleep_by_date_range: Retrieve raw sleep log data for a specified date range (up to 100 days). Requires two parameters: startDate and endDate, both in the format YYYY-MM-DD.
• Profile:
  • get_profile: Retrieve the user's Fitbit profile information.

Planned Endpoints

In the future, support for more Fitbit API endpoints is planned, including but not limited to:

• Activity data
• Heart rate monitoring
• Blood pressure records
• Height, etc.

📦 Installation

1. Clone the repository:

   git clone [repository_url]
   cd fitbit-mcp-server
   

2. Install dependencies:

   npm install
   

3. Configure environment variables:

   • Create a .env file and add the following content:

     FITBIT_CLIENT_ID=your_client_id
     FITBIT_CLIENT_SECRET=your_client_secret
     

4. Build the project:

   npm run build
   

5. Run the server:

   npm start
   

📚 Integration with Claude

To integrate this server into a Claude environment, follow these steps:

1. Add the files in the built dist folder to Claude's tool path.
2. Add the following content to Claude's configuration file (usually config.json):

   {
     "tools": [
       {
         "name": "get_weight",
         "description": "Retrieve weight data for a specified time period.",
         "parameters": {
           "type": "object",
           "properties": {
             "period": {
               "type": "string",
               "enum": ["1d", "7d", "30d", "3m", "6m", "1y"],
               "description": "Specify the time period. Must be '1d', '7d', '30d', '3m', '6m', or '1y'."
             }
           }
         }
       },
       {
         "name": "get_sleep_by_date_range",
         "description": "Retrieve sleep data for a specified date range.",
         "parameters": {
           "type": "object",
           "properties": {
             "startDate": {
               "type": "string",
               "format": "date",
               "description": "Specify the start date in the format 'YYYY-MM-DD'."
             },
             "endDate": {
               "type": "string",
               "format": "date",
               "description": "Specify the end date in the format 'YYYY-MM-DD'."
             }
           }
         }
       },
       {
         "name": "get_profile",
         "description": "Retrieve the user's Fitbit profile information.",
         "parameters": {}
       }
     ]
   }
   

💻 Usage Examples

Basic Usage

Here are the available tools after the server is running:

• get_weight: Returns weight data for a specified time period.
  • Parameters: period (string, required) - Specify the time period. Must be one of the following values: "1d", "7d", "30d", "3m", "6m", "1y".
  • Conceptual example usage: get_weight(period="7d")
• get_sleep_by_date_range: Returns sleep data for a specified date range.
  • Parameters:
    • startDate (string, required) - Specify the start date in the format YYYY-MM-DD.
    • endDate (string, required) - Specify the end date in the format YYYY-MM-DD.
  • Conceptual example usage: get_sleep_by_date_range(startDate="2025-04-01", endDate="2025-04-30")
• get_profile: Returns the user's Fitbit profile information.
  • Parameters: None
  • Conceptual example usage: get_profile()

🔧 Technical Details

• The source code is located in the src/ directory.
• After modifying the TypeScript files, run npm run build to rebuild the project.
• If the server is already running in the Claude environment, restart Claude to ensure it recognizes the latest build.