Ouramcp
Wire Oura Ring sleep, activity, and heart-rate data into Claude Code or Cursor while you build health, wellness, or productivity agents.
Overview
io.github.davidmosiah/ouramcp is a MCP server for the Build phase that connects AI coding agents to Oura Ring sleep, activity, and heart-rate data over OAuth.
What is this MCP server?
- Privacy-first unofficial server that exposes Oura health, sleep, activity, and heart-rate data to MCP clients
- OAuth via OURA_CLIENT_ID, OURA_CLIENT_SECRET, and OURA_REDIRECT_URI, with optional oura-mcp-server setup storing secrets
- Tokens default to ~/.oura-mcp/tokens.json with optional OURA_TOKEN_PATH and OURA_PRIVACY_MODE
- Published on npm as oura-mcp-unofficial v0.4.6 with stdio transport for Claude Code, Cursor, and other MCP hosts
- Designed for AI agents that summarize recovery, correlate sleep with work output, or back wellness SaaS features
- npm package identifier: oura-mcp-unofficial at version 0.4.6
- Transport: stdio per server.schema.json
- Default token path: ~/.oura-mcp/tokens.json; optional config at ~/.oura-mcp/config.json via setup CLI
What problem does it solve?
Building an agent that needs Oura metrics forces you to handle OAuth, token files, and API wiring instead of focusing on your product logic.
Who is it for?
Solo builders with an Oura account who want sleep and activity context inside Claude Code or Cursor while prototyping health or productivity features.
Skip if: Teams that need an official Oura partnership, lack an Oura ring or API app, or want a non-MCP REST SDK only.
What do I get? / Deliverables
After you register the stdio server and complete OAuth setup, your agent can call Oura-backed MCP tools using tokens stored under ~/.oura-mcp.
- Stdio MCP server registered in your agent client for Oura queries
- OAuth tokens and config under ~/.oura-mcp for repeatable agent sessions
- Agent-accessible Oura sleep, activity, and heart-rate context for your app or workflows
Recommended MCP Servers
Journey fit
Solo builders adopt this server when they are actively integrating third-party APIs into an agent-backed product, not when they are only researching markets or shipping unrelated code. It is a stdio MCP bridge to the Oura OAuth API, which belongs on the integrations shelf alongside other external-service connectors agents call at build time.
How it compares
Oura Ring MCP OAuth bridge, not a generic wellness prompt skill or official Oura mobile app.
Common Questions / FAQ
Who is io.github.davidmosiah/ouramcp for?
It is for solo and indie developers who already use Oura and want their AI coding agent to read sleep, activity, and heart-rate data through MCP while they build integrations.
When should I use io.github.davidmosiah/ouramcp?
Use it during the build phase when your agent, API, or SaaS feature needs live Oura OAuth data and you are ready to configure npm stdio MCP plus Oura Developer credentials.
How do I add io.github.davidmosiah/ouramcp to my agent?
Install the npm package oura-mcp-unofficial, run oura-mcp-server setup to store OAuth settings in ~/.oura-mcp/config.json, then add a stdio MCP entry in Claude Code or Cursor with the required OURA_* environment variables.