Oura MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Oura MCP ServerGet my daily readiness for yesterday."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Oura MCP Server
A remote Model Context Protocol (MCP) server for accessing Oura Ring data over Streamable HTTP.
This server is designed for deployment behind HTTPS, such as a self-hosted Coolify instance, so it can be added to Claude.ai as a Custom Connector. It uses the MCP TypeScript SDK's StreamableHTTPServerTransport, not stdio and not the legacy SSE transport.
Setup
Prerequisites
Node.js 22+
pnpm
Oura account
Installation
Clone the repository
Run:
pnpm install
pnpm run buildRelated MCP server: Oura Ring MCP Server
Configuration
Environment Variables
Create a .env file for local development only:
PORT=3000
MCP_ALLOWED_HOSTS=oura-mcp.mydomain.com
OURA_PERSONAL_ACCESS_TOKEN=your_tokenDo not commit .env or any real Oura token. In Coolify, set OURA_PERSONAL_ACCESS_TOKEN in the Resource environment variable UI.
You can also set MCP_ALLOWED_HOSTS to your connector hostname, for example oura-mcp.mydomain.com, to restrict accepted Host headers.
Obtaining An Oura Token
Log in to Oura Cloud Console.
Create a Personal Access Token at Personal Access Tokens.
Store it only as
OURA_PERSONAL_ACCESS_TOKENin your deployment environment.
Local Usage
pnpm run build
PORT=3000 OURA_PERSONAL_ACCESS_TOKEN=placeholder pnpm startThe MCP endpoint is:
http://localhost:3000/mcpDocker
Build and run locally:
docker build -t oura-mcp .
docker run --rm -p 3000:3000 -e OURA_PERSONAL_ACCESS_TOKEN=your_token oura-mcpCoolify Deployment
Push this repository to your GitHub account, or use Coolify's Public Repository option with your fork URL.
In Coolify, create a new Project if needed.
Add a new Resource.
Choose your Git repository, or choose Public Repository and paste the repository URL.
Select Dockerfile as the build pack.
Confirm the Dockerfile path is
Dockerfile.Set Port Exposes to
3000.In Environment Variables, add:
OURA_PERSONAL_ACCESS_TOKEN=<your Oura personal access token>Do not put the token in code,
.env.example, build arguments, or logs.Optional but recommended: add
MCP_ALLOWED_HOSTSwith only the hostname from your FQDN, for example:MCP_ALLOWED_HOSTS=oura-mcp.mydomain.comSet the Resource FQDN/domain field, for example:
https://oura-mcp.mydomain.comDeploy. Coolify will route HTTPS traffic to the container and provision a Let's Encrypt certificate for the FQDN.
Your final Claude Custom Connector URL should be:
https://oura-mcp.mydomain.com/mcpMCP Handshake Check
After deployment, replace the URL below with your actual HTTPS FQDN:
curl -i https://oura-mcp.mydomain.com/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl-handshake","version":"1.0.0"}}}'A healthy response returns HTTP 200, an mcp-session-id response header, and a JSON-RPC result containing the server info for oura-provider.
Available Resources
personal_info- User profiledaily_activity- Activity summariesdaily_readiness- Readiness scoresdaily_sleep- Sleep summariessleep- Detailed sleep datasleep_time- Sleep timingworkout- Workout datasession- Session datadaily_spo2- SpO2 measurementsrest_mode_period- Rest periodsring_configuration- Ring configdaily_stress- Stress metricsdaily_resilience- Resilience metricsdaily_cardiovascular_age- CV agevO2_max- VO2 max data
Available Tools
For date-based resources, use tools like get_daily_sleep with startDate and endDate parameters (YYYY-MM-DD).
This server cannot be deployed
Maintenance
Related MCP Connectors
Multi-tenant hosted MCP server for Oura Ring — 21 read-only tools, OAuth per user.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Pace is a remote MCP server that exposes wearable and fitness data to Claude via the Model Context Protocol. It connects to Garmin, Oura, Whoop, Polar, Fitbit and 20+ devices and provides 15 tools for querying sleep, activity, recovery, and training data. Hosted on Google Cloud Run, OAuth 2.1 authentication, Streamable HTTP transport. Instructions: First you need to create an account at: https://pacetraining.co and connect your wearables. After that you can connect the remote Server via Custom Connector in Claude and OAuth 2.1 Flow startet.
Connect your Oura Ring account and enable access to your wellness data in apps and automations. In…
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to query Oura Ring health data (sleep, readiness, activity, heart rate, SpO2, stress) via a remote MCP server.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to access and query Oura Ring health data including sleep, activity, readiness, heart rate, and more via the Oura API.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Desktop and Claude Code to access your personal Oura Ring health data—including sleep, readiness, activity, heart rate, and workouts—through local MCP tools.6 npmMIT
- AlicenseBqualityBmaintenanceMCP server for accessing Oura Ring data from Claude Code and claude.ai, providing summarized health metrics and raw API data.11MIT