Connect your AI Agents to Oura in minutes
Available tools
list_daily_activity
List daily activity summaries including steps, calories, and activity scores. Filter by start_date/end_date. Use next_token for pagination.
get_daily_activity
Get a specific daily activity record by document ID. Use list_daily_activity to find valid IDs.
list_heartrate
List heart rate samples with BPM and source. Filter by start_datetime/end_datetime (ISO 8601). Use next_token for pagination.
list_daily_readiness
List daily readiness scores with contributors like HRV balance, body temperature, and sleep. Filter by start_date/end_date. Use next_token for pagination.
get_daily_readiness
Get a specific daily readiness record by document ID. Use list_daily_readiness to find valid IDs.
list_rest_mode_periods
List rest mode periods when the user activated rest mode. Filter by start_date/end_date. Use next_token for pagination.
get_rest_mode_period
Get a specific rest mode period by document ID. Use list_rest_mode_periods to find valid IDs.
list_sessions
List guided breathing and meditation sessions. Filter by start_date/end_date. Use next_token for pagination.
get_session
Get a specific session by document ID. Use list_sessions to find valid IDs.
list_daily_sleep
List daily sleep scores with pagination. Filter by start_date/end_date (YYYY-MM-DD). Use next_token from page_info for next page.
get_daily_sleep
Get a specific daily sleep record by document ID. Use list_daily_sleep to find valid IDs.
list_sleep_sessions
List detailed sleep sessions with heart rate, HRV, and sleep stages. Filter by start_date/end_date. Use next_token for pagination.
How to set up Merge Agent Handler
In an mcp.json file, add the configuration below, and restart Cursor.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.
Make sure Claude is using the Node v20+.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "yMt*****"
14 }
15 }
16 }
17}Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "<ah-production-access-key>"
14 }
15 }
16 }
17 }In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".
You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.
Learn more in the official documentation ↗
1{
2 "inputs": [
3 {
4 "type": "promptString",
5 "id": "agent-handler-auth",
6 "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7 "password": true
8 }
9 ],
10 "servers": {
11 "agent-handler": {
12 "type": "stdio",
13 "command": "npx",
14 "args": [
15 "-y",
16 "mcp-remote@latest",
17 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18 "--header",
19 "Authorization: Bearer ${input:agent-handler-auth}"
20 ]
21 }
22 }
23}FAQs on using Merge's Oura MCP server
FAQs on using Merge's Oura MCP server
What is an Oura Ring MCP?
It’s an MCP server that lets you access data and functionality from Oura via tools. Your agents can invoke these tools to retrieve your daily readiness score, see your sleep sessions over the pages week, get a certain rest mode period, and more.
Oura Ring doesn’t currently support their own “official” MCP server. But you can use one from a 3rd-party platform, like Merge Agent Handler.
What are some examples of using an Oura Ring MCP?
Here are a few examples of how your agents can use the server:
- Daily status briefing: Deliver a daily readiness, sleep, and activity summary to guide how someone should pace their day
- Workload and scheduling alignment: Adjust calendars and workload recommendations based on recovery status to reduce burnout risk
- Training personalization: Personalize workout selection and intensity using current readiness and recent strain patterns
- Sleep and recovery optimization: Provide recovery coaching by identifying the biggest drivers of poor sleep and recommending targeted behavior changes
- Travel recovery support: Support travel and jet lag recovery with guidance tailored to sleep debt and circadian disruption signals
- Anomaly detection and attribution: Detect unusual changes in sleep or recovery and attributing them to likely contributing factors such as late nights, alcohol, illness, or overtraining
What makes Merge Agent Handler’s Oura Ring MCP server better than alternative Oura Ring MCP servers?
Here are some reasons:
- Production-oriented infrastructure: Merge Agent Handler is built around maintained connectors, authentication, permissioning, monitoring, and security controls
- Authentication and credential handling. Merge manages authentication, permissions, and credential handling as part of the platform, rather than leaving that work to each MCP deployment
- Security controls and DLP: Agent Handler includes a security gateway that scans tool inputs and responses for sensitive data, along with default and custom DLP rules that can block, redact, or mask sensitive fields
- Real-time observability and auditability: Agent Handler comes with tool-call logging, real-time logs, and a complete audit trail; the logs are reviewable and searchable for debugging and auditing
- Customization and extension: Agent Handler includes "Connector Studio", which lets you add and modify connectors and tools
Can I set custom security rules for Oura Ring tool calls in Merge Agent Handler?
Yes, Agent Handler includes default security rules and custom security rules, and its DLP layer can be configured to block, redact, or mask sensitive data in tool inputs and outputs.
Here are some custom rules you can set:
- Just use read-only summaries and no raw exports: Only allow read-only “daily summary” tools, and block any attempt to export raw sleep stages, heart rate, or minute-level timelines into messages or tickets
- Aggregate with cohort minimums and no drill-down: Require aggregation and minimum cohort thresholds, and block any report that can be filtered down to a single individual
- Block individual access: Deny all individual-level Oura access for manager identities, and only allow anonymized rollups with limited segmentation
- Block raw signals or exact scores: Allow risk band indicators such as low, medium, and high, and prohibit storing or sharing the underlying biometric signals or exact scores outside the approved system
How can I start using Merge Agent Handler’s Oura Ring MCP server?
You can take these steps:
1. Create or sign in to your Merge Agent Handler account, then open the Agent Handler dashboard.
2. Create a Tool Pack for your Oura workflow, since Tool Packs define which tools the agent is allowed to call.
3. Connect Oura by authenticating the Oura connector for the Registered User who will be making the tool calls.
4. Get your MCP endpoint URL for that Tool Pack and Registered User, using the standard Agent Handler MCP URL pattern that includes both IDs.
5. Connect an MCP client to that MCP endpoint, using the required auth header or bearer token for your Agent Handler account.
6. Refresh tools in your MCP client so the Oura tools appear, then run a few safe read actions first to validate behavior.
7. Verify the run in Agent Handler logs so you can confirm the tool arguments, responses, and audit trail look correct before expanding scope.
Ready to try it out?
Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now
