Eliu243 Oura Mcp Server 2
Register an alternate Smithery package slug for the same Oura Ring MCP so secure, authenticated wellness access works in CI, staging, or a second agent profile without conflicting with your primary se
Overview
ai.smithery/eliu243-oura-mcp-server-2 is an MCP server for the Build phase that offers a second Smithery remote for secure, authenticated Oura Ring workflow access.
What is this MCP server?
- Smithery package @eliu243/oura-mcp-server-2 with distinct remote URL from the primary listing
- Secure Oura account connection for authenticated workflow access
- Streamable-http MCP on Smithery with Bearer smithery_api_key
- Version 1.16.0 aligned with github.com/eliu243/oura-mcp-server
- Supports generating or rotating credentials without tearing down your main agent MCP block
- Server version: 1.16.0
- Remote path: @eliu243/oura-mcp-server-2/mcp
- Repository: github.com/eliu243/oura-mcp-server
What problem does it solve?
You need another Smithery MCP endpoint for Oura—staging, key rotation, or parallel agents—without overwriting the remote URL you already use in production.
Who is it for?
Builders running two MCP configs (dev/prod), rotating Smithery credentials, or standardizing onboarding docs with a dedicated package slug.
Skip if: Anyone who only needs one Oura connection—install a single Oura MCP entry to avoid duplicate tools.
What do I get? / Deliverables
You get a distinct Smithery remote that still ties into Oura authorization so a separate agent profile can query wellness data independently.
- Separate Smithery remote endpoint for Oura-backed agent workflows
- Isolated auth path for non-production experimentation
- Same upstream capability surface as eliu243 Oura MCP v1.16.0 when configs match
Recommended MCP Servers
Journey fit
A second Smithery listing matters during Build when you maintain parallel MCP configs—for example production versus experiments—while still integrating Oura. integrations is where duplicate remote endpoints are cataloged and wired; this variant emphasizes secure authenticated workflow setup.
How it compares
Alternate Smithery slug for the same Oura MCP family, not a different wearable platform.
Common Questions / FAQ
Who is ai.smithery/eliu243-oura-mcp-server-2 for?
Solo builders who already use Oura and need a second Smithery-hosted MCP URL for staging, backups, or isolated agent profiles.
When should I use ai.smithery/eliu243-oura-mcp-server-2?
Use it when you are splitting workflow credentials or testing OAuth while keeping your primary ai.smithery/eliu243-oura-mcp-server config untouched.
How do I add ai.smithery/eliu243-oura-mcp-server-2 to my agent?
Configure https://server.smithery.ai/@eliu243/oura-mcp-server-2/mcp with Bearer {smithery_api_key}, link Oura per server instructions, and enable only one Oura MCP per profile unless you intend redundant tools.