Skip to main content
Glama
tomekkorbak

Oura MCP Server

by tomekkorbak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OURA_API_TOKENYesYour personal access token from the Oura Developer Portal

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_sleep_dataB
Get sleep data for a specific date range.

Args:
    start_date: Start date in ISO format (YYYY-MM-DD)
    end_date: End date in ISO format (YYYY-MM-DD)

Returns:
    Dictionary containing sleep data
get_readiness_dataB
Get readiness data for a specific date range.

Args:
    start_date: Start date in ISO format (YYYY-MM-DD)
    end_date: End date in ISO format (YYYY-MM-DD)

Returns:
    Dictionary containing readiness data
get_resilience_dataB
Get resilience data for a specific date range.

Args:
    start_date: Start date in ISO format (YYYY-MM-DD)
    end_date: End date in ISO format (YYYY-MM-DD)

Returns:
    Dictionary containing resilience data
get_today_sleep_dataB
Get sleep data for today.

Returns:
    Dictionary containing sleep data for today
get_today_readiness_dataB
Get readiness data for today.

Returns:
    Dictionary containing readiness data for today
get_today_resilience_dataC
Get resilience data for today.

Returns:
    Dictionary containing resilience data for today

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 6 tools

Disambiguation3/5

The tools have clear distinctions between readiness, resilience, and sleep data types, but there is significant overlap between the 'get_X_data' and 'get_today_X_data' pairs. An agent might confuse which tool to use for today's data versus a date range, though the descriptions clarify the difference.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes (e.g., 'get_readiness_data', 'get_today_sleep_data'). The naming is predictable and uniform across all six tools.

Tool Count4/5

Six tools are reasonable for a health/fitness data server, covering three data types with both date-range and today-specific variants. It's slightly over-scoped as the 'today' tools could be handled by the date-range tools with default parameters, but it's still well within an appropriate range.

Completeness3/5

The server provides read-only access to readiness, resilience, and sleep data, which aligns with Oura's typical API capabilities. However, there are notable gaps: no tools for writing or updating data (e.g., setting goals or annotations), and no coverage of other Oura metrics like activity or heart rate, limiting the surface for comprehensive health tracking.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources