Skip to the content

Oura for agents

Other. MCP servers, the command line and skills for connecting an agent to Oura.

Build an agent with Oura

Official server
none identified
Sourced servers by others
12
Command line
none curated
Vendor skills
none

Official server

We have not identified a server published by Oura's owner in the MCP Registry (read ). One may exist, in the registry under a name we have not matched or outside it. The servers below are by other publishers.

How it is reached

As Oura's vendor states it, read from its own page on the day given.

  • Through its API. Each user signs in to their own account. An app may have 10 users before the vendor reviews it. The vendor's page, read .

Its terms, for an agent

Clauses of Oura's terms that bear on an agent's use, each the page's own words, which a person chose and a nightly check looks for on the page. They are the vendor's words, not legal advice and not all of the terms: read the page. See how terms are checked.

  • Use with AI · §4(d) · in effect from
    The page says: “access and process such Oura Data or User Data solely through the MCP Server”

    The page, read ; the words were on it .

  • Aggregators and relays · §2(c) · in effect from
    The page says: “no Aggregator shall relay, transmit, transfer, make available, disclose, distribute, redistribute, or otherwise provide or permit any Oura Data or User Data”

    The page, read ; the words were on it .

Servers by other publishers

12 servers for Oura that name a public repository or a package, or whose tools we could read. Anyone can publish one, and we have not read their code: check the publisher and the source before giving one a credential.

In this order: live servers before deprecated ones, first-party first, a known vulnerability last, then more downloads, then a more recent push, then by name. There is no score, and the number of tools is not part of the order: fewer is not better. Tools are what a server listed to a client with no credential, or what its package listed when run with no network, downloads are from npm and pypistats, the last push from GitHub and vulnerabilities from OSV; a server's own page has the day each was read, and "not read" means we have no figure, not that there is none. See how this directory is made.

ServerPublisherReachToolsDownloads a weekLast pushVulnerabilities
io.github.jordanburke/oura-ring-mcp-serverSourcednpmnot read960not readnone known
io.github.mitchhankins01/oura-ring-mcpSourcednpmnot read150not readnone known
Oura Ringio.github.YasuakiOmokawa/oura-mcpSourcednpmnot read130not readnone known
io.github.proscar87/oura-mcpSourcedPyPInot read95not readnone known
Oura Ring (read-only)io.github.royreznik/oura-ring-mcpSourcednpmnot read72not readnone known
Oura Ringio.github.AntVsl/oura-mcpSourcedPyPIContainer imagenot read51not readnone known
Oura Ringio.github.osjayaprakash/oura-ring-python-mcpSourcedPyPIContainer imagenot read15not readnone known
ai.smithery/eliu243-oura-mcp-serverSourcedremotenot answeringnot readnot readnot checked
ai.smithery/eliu243-oura-mcp-server-2Sourcedremotenot answeringnot readnot readnot checked
ai.smithery/eliu243-oura-mcp-server-eliuSourcedremotenot answeringnot readnot readnot checked
Oura MCP by usefulapiio.usefulapi/ouraInspectedremote10not readnot readnot checked
MCP for Ouralink.smirnov/mcp-ouraSourcedremoteasks to sign innot readnot readnot checked

Changes for Oura

None in the last 30 days. The log began on , and nothing older was recorded.

A change is a difference between two readings of public records, not a review. Oura in the log · How the log is made · Oura's Atom feed

A server is listed for Oura when we have named it as the system's official server, when its registry title or the last part of its registry name names Oura as whole words, or when it is published at Oura's own domain. See how this directory is made.

Built from agent catalog version 2026-11-18.1 of , from the MCP Registry as read on . A listing here is not an endorsement: anyone can publish a server, and we have not read its code. Names, descriptions and addresses are the publisher's own. See how this directory is made, and tell us about a wrong entry through the contact page.