MCP servers · ashwanthramkl

WHOOP MCP Server

A local, read-only MCP server that gives an MCP client access to WHOOP v2 fitness data, cached locally in SQLite.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

This is a local Python process that speaks MCP over stdio and exposes WHOOP v2 data, including profile, body measurements, cycles, recoveries, sleeps and workouts, through 17 tools. Authentication uses direct OAuth against a WHOOP developer app that you register yourself. Fetched records are mirrored into a local SQLite cache, and the data can be exported as CSV, JSONL or Parquet. Read tools accept a flag that bypasses the cache and returns live WHOOP API responses. Errors are returned as structured envelopes.

The server is aimed at people who want an LLM such as Claude Desktop or Claude Code to answer questions about their own WHOOP records. Typical uses include syncing the last 30 days, viewing a joined daily summary of cycle, recovery, primary sleep and workouts, and exporting workouts to a file. A bundled analysis skill, whoop-insights, reads the cache, computes personal baselines for HRV, recovery, sleep and strain, flags anomalies, runs two correlations and can produce an HTML dashboard.

The server can be run with uvx without cloning the repository, or installed from source into a virtual environment and registered in the MCP client configuration. Setup requires the uv tool and a WHOOP developer app with OAuth credentials. Data stays on the local machine apart from the authenticated calls made to the WHOOP v2 API. The cache file is created with restricted permissions.

Limitations and requirements

Requires a WHOOP developer app registered by the user, with OAuth authentication. Requires the uv tool for the uvx install path. The server is read-only. The publisher describes it as pre-1.0: tool names, response shapes and error codes are not frozen, and breaking changes may appear in minor version updates. The publisher recommends pinning the minor version in CI.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.AshwanthramKL/whoop-mcp

    Read-only WHOOP v2 data for MCP clients, with local SQLite cache and CSV/JSONL/Parquet exports.

    v0.8.5
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026