Skip to main content
Glama
jordanburke

oura-ring-mcp-server

by jordanburke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HOSTNoHost for httpStream.0.0.0.0
PORTNoPort for httpStream.3000
OURA_SCOPESNoSpace-separated scopes.full read set
OURA_API_KEYNoLegacy personal access token (Bearer).
OURA_SANDBOXNoUse sandbox data.false
OURA_CLIENT_IDNoOura OAuth2 client ID.
TRANSPORT_TYPENoTransport type.stdio
OURA_TOKEN_STORENoPath to token store.~/.config/oura-ring-mcp/tokens.json
OURA_REDIRECT_URINoRedirect URI for login.http://localhost:8080/callback
OURA_CLIENT_SECRETNoOura OAuth2 client secret.
OURA_TELEMETRY_FILENoWrite NDJSON telemetry events.
OURA_TELEMETRY_CONSOLENoConsole telemetry.true

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
logging
{}
completions
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
infoA

Returns identity and build information for this server (name, version, build commit, runtime, capability counts)

oura_dataA

Fetch data from the Oura Ring API v2.

Pick a collection and provide the matching date range:

  • Daily collections use start_date/end_date (YYYY-MM-DD). If both are omitted, the last 7 days are returned.

  • Time-series collections (heartrate, ring_battery_level) use start_datetime/end_datetime (ISO-8601), or latest: true.

  • personal_info takes no parameters; ring_configuration is a plain list.

  • Any list collection with a document id can be fetched directly via document_id. Large lists paginate: pass the returned next_token to fetch the next page.

Available collections:

  • daily_activity: Daily activity summary: steps, calories, activity score.

  • daily_sleep: Daily sleep summary and sleep score.

  • daily_readiness: Daily readiness summary and readiness score.

  • daily_spo2: Daily average blood oxygen (SpO2) percentage.

  • daily_stress: Daily stress and recovery high/normal durations.

  • daily_resilience: Daily resilience level derived from recovery metrics.

  • daily_cardiovascular_age: Daily cardiovascular age estimate.

  • vO2_max: VO2 max (cardiorespiratory fitness) estimates.

  • sleep: Detailed per-period sleep sessions (stages, HRV, heart rate).

  • sleep_time: Recommended/ideal bedtime windows.

  • session: Guided/unguided moment sessions (meditation, breathing, rest).

  • workout: Recorded workouts with intensity, calories, and duration.

  • tag: Legacy user-entered tags.

  • enhanced_tag: Enhanced user-entered tags (current tag model).

  • rest_mode_period: Rest mode periods (recovery/illness) the user enabled.

  • heartrate: Time-series heart rate samples.

  • ring_battery_level: Time-series ring battery level samples.

  • ring_configuration: Ring hardware configuration records (size, color, firmware, design).

  • personal_info: The user's personal info: age, weight, height, biological sex, email.

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

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: 'info' returns server metadata, while 'oura_data' fetches Oura Ring API data. There is no overlap or ambiguity.

Naming Consistency3/5

With only two tools, a consistent naming pattern is hard to establish. 'info' is a noun, while 'oura_data' uses underscore separation. The names are not chaotic but lack a strong, predictable pattern.

Tool Count3/5

Having only two tools for a server that covers a wide range of health data (18+ collections) feels thin. The generic 'oura_data' tool consolidates all data retrieval, which is efficient but potentially overloaded.

Completeness3/5

The server covers read access to many Oura Ring data collections, but lacks any write operations (create, update, delete). For a comprehensive API surface, this is a notable gap.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources