An MCP server for the Oura Ring API v2 that exposes Oura sleep, activity, readiness, heart rate, and workout data to MCP clients via OAuth. It also provides tools to authenticate, check token status, clear stored auth, list supported API paths, and make generic GET requests to Oura endpoints.
From the registry: MCP server for Oura Ring API v2 (sleep, activity, readiness, heart rate, workouts).
$ npx @yasuakiomokawa/oura-mcp configurePlease install the `oura-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Register an Oura developer app** — Create an Oura developer application to obtain OAuth credentials for the server. (https://cloud.ouraring.com/oauth/applications/)
- **Configure the redirect URI** — Set the app redirect URI exactly to http://localhost:54321/callback, or http://localhost:<your-callback-port>/callback if you customize OURA_CALLBACK_PORT. (https://cloud.ouraring.com/oauth/applications/)
- **Enable required Oura API scopes** — Enable the read scopes you need in the Oura developer app, such as Email, Personal info, Daily activity, Heart rate, Workout, Tag, Session, SpO2, Ring configuration, Stress, and Heart health. (https://cloud.ouraring.com/oauth/applications/)
- **Run the OAuth configuration wizard once** — Run the configure command once to enter your Oura Client ID and Client Secret, complete browser OAuth, and save tokens under ~/.config/oura-mcp/. Run: `npx @yasuakiomokawa/oura-mcp configure`
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@yasuakiomokawa/oura-mcp"]
- optional environment variables:
- `OURA_CLIENT_ID`: Oura OAuth client ID. Optional if you use the recommended config-file wizard; required if supplying credentials via environment variables instead. (example: `<your-oura-client-id>`)
- `OURA_CLIENT_SECRET`: Oura OAuth client secret. Must be set together with OURA_CLIENT_ID. Optional if you use the recommended config-file wizard; required if supplying credentials via environment variables instead. (example: `<your-oura-client-secret>`)
- `OURA_CALLBACK_PORT`: Local callback port for OAuth redirect. If set, the redirect URI in your Oura developer app must match http://localhost:<your-callback-port>/callback. (example: `<your-callback-port>`)
- `OURA_LOG_LEVEL`: Optional log level for verbose stderr logging during troubleshooting. (example: `<log-level>`)
Note: Recommended setup is to run `npx @yasuakiomokawa/oura-mcp configure` once, which stores clientId/clientSecret and OAuth tokens in `~/.config/oura-mcp/` with 0600 permissions. The canonical MCP config itself is stdio using `npx -y @yasuakiomokawa/oura-mcp`. Do not pass secrets in args; if not using the config-file wizard, supply credentials via env instead.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.OURA_CLIENT_IDrequiredOura OAuth client ID used to authenticate the server with the Oura API.OURA_CLIENT_SECRETrequiredOura OAuth client secret used together with the client ID.OURA_CALLBACK_PORTLocal callback port for OAuth redirect handling; must match the Oura app redirect URI if customized.AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.