whoop-mcp-server

Frenck12/whoop-mcp-server

3.2

If you are the rightful owner of whoop-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

The Whoop MCP Server provides secure access to Whoop fitness data using OAuth2 authentication, ensuring user privacy and local data processing.

Tools
5
Resources
0
Prompts
0

Whoop MCP Server: Secure Access to Fitness Data 🚀🏃‍♂️

GitHub Repo Size GitHub Issues GitHub Stars

Overview

Welcome to the Whoop MCP Server! This project provides a secure way for the Claude Desktop application to access Whoop fitness and health data. With a focus on user privacy and data protection, this server utilizes OAuth2 authentication and offers local processing capabilities.

You can download the latest version of the server here. Follow the instructions to execute the server on your local machine.

Features

  • OAuth2 Authentication: Ensures secure access to your Whoop data.
  • Local Processing: Keeps your data on your device, enhancing privacy.
  • Comprehensive Privacy Policy: Clearly outlines how your data is used and protected.
  • Tools for Fitness: Offers seven tools to help with sleep, recovery, workouts, and more.

Getting Started

Prerequisites

To run the Whoop MCP Server, you need:

  • Node.js (version 14 or later)
  • npm (Node package manager)

Installation

  1. Clone the repository:

    git clone https://github.com/Frenck12/whoop-mcp-server.git

  2. Navigate to the project directory:

    cd whoop-mcp-server

  3. Install the dependencies:

    npm install

Running the Server

To start the server, run:

npm start

You can then access the server at http://localhost:3000.

Configuration

Before using the server, configure your OAuth2 credentials. Create a .env file in the root directory and add the following:

CLIENT_ID=your_client_id
CLIENT_SECRET=your_client_secret
REDIRECT_URI=your_redirect_uri

Replace the placeholders with your actual credentials from Whoop.

API Documentation

The Whoop MCP Server exposes a set of APIs to interact with your fitness data. Below are the main endpoints:

Authentication

  • POST /auth: Initiates the OAuth2 flow. Redirects the user to Whoop for authentication.

Data Retrieval

  • GET /data/sleep: Retrieves sleep data for the authenticated user.
  • GET /data/recovery: Retrieves recovery metrics.
  • GET /data/workouts: Fetches workout history and statistics.

Tools

The server includes several tools to help you manage your fitness journey:

  1. Sleep Analysis: Provides insights into your sleep patterns.
  2. Recovery Metrics: Helps track recovery and readiness for workouts.
  3. Workout Logs: Maintains a history of your workouts.
  4. Goal Setting: Allows you to set and track fitness goals.
  5. Data Visualization: Displays your fitness data in easy-to-read charts.
  6. Notifications: Sends alerts for recovery and workout reminders.
  7. Privacy Settings: Lets you manage how your data is shared.

Contributing

We welcome contributions! If you want to help improve the Whoop MCP Server, follow these steps:

  1. Fork the repository.
  2. Create a new branch for your feature or bug fix.
  3. Make your changes.
  4. Submit a pull request.

Code of Conduct

Please adhere to our while contributing to this project.

License

This project is licensed under the MIT License. See the file for details.

Support

If you encounter any issues or have questions, please check the Releases section for updates and troubleshooting tips.

Topics

This repository covers various topics related to fitness and health, including:

  • API: Building and using APIs for fitness data.
  • Claude: Integration with the Claude Desktop application.
  • Desktop: Focus on desktop application compatibility.
  • Fitness: Tools and metrics for fitness enthusiasts.
  • Health: Managing health data securely.
  • JavaScript: The primary programming language used.
  • MCP: The server architecture for data processing.
  • Node.js: The runtime environment for executing JavaScript code.
  • OAuth: Authentication method used for secure access.
  • Whoop: Integration with Whoop fitness trackers.

Community

Join our community to discuss features, report issues, or share your experiences. You can find us on:

  • GitHub Discussions: Share ideas and ask questions.
  • Twitter: Follow us for updates and news.
  • Discord: Join our chat for real-time discussions.

Acknowledgments

We appreciate the support from the Whoop community and the open-source developers who contributed to this project. Your feedback helps us improve the Whoop MCP Server.

For updates, please check the Releases section regularly.

Visuals

Your personal fitness dashboard

Tools to enhance your fitness journey

FAQs

What is Whoop?

Whoop is a fitness tracker that provides insights into your health and performance. It tracks metrics like sleep, recovery, and workouts.

How does OAuth2 work?

OAuth2 is an authorization framework that allows third-party applications to access user data without sharing passwords. It uses tokens to grant access.

Can I run this server on a cloud platform?

Yes, you can deploy the Whoop MCP Server on cloud platforms like AWS, Heroku, or DigitalOcean.

Is my data safe?

Yes, we prioritize user privacy and security. The server processes data locally, and we follow a comprehensive privacy policy.

How can I contribute?

You can contribute by reporting issues, suggesting features, or submitting code improvements through pull requests.

For more questions, feel free to reach out via GitHub Issues or our community channels.