Model Context Protocol (mcp) Server + Strava Oauth

🚀 Model Context Protocol (MCP) Server + Strava OAuth

This is a server based on the Model Context Protocol (MCP), supporting remote MCP connections and featuring built - in Strava OAuth login functionality. Users can connect to your MCP server and log in using their Strava accounts.

🚀 Quick Start

Prerequisites

• A Strava account
• A Cloudflare account
• Node.js and npm installed
• Wrangler CLI installed (npm install -g wrangler)

Steps

1. Clone the repository:

   git clone https://github.com/kw510/strava-mcp.git
   cd strava-mcp
   npm install
   

2. Set up your Strava API credentials (see Setting up Strava API Credentials).

3. Set up a Cloudflare KV namespace:

   wrangler kv:namespace create "OAUTH_KV"
   

   Update the wrangler.toml file with the generated KV ID.

4. Deploy to Cloudflare:

   wrangler deploy
   

✨ Features

OAuth Provider

• Implements the OAuth 2.0 flow using the workers - oauth library.
• Supports Strava's authorization code flow.
• Configures callback URLs and client ID/secret for authentication.

Persistent MCP

• Stores connection states in Cloudflare KV storage.
• Manages persistent sessions and user data using the durable - object library.
• Implements secure session management and state storage.

MCP Proxy

• Creates an MCP proxy using the @cloudflare/mcp - proxy library.
• Supports bidirectional communication via WebSocket and HTTP.
• Provides access to remote models and handles requests and responses.

📦 Installation

Setting up Strava API Credentials

Production Environment

1. Go to Strava's API settings and create a new application.

2. Configure your application:

   • Application Name: Choose a name for your application.
   • Category: Select an appropriate category.
   • Website: Your website URL.
   • Application Description: Briefly describe your application.
   • Authorized Callback Domain: mcp - strava - oauth.<your - subdomain>.workers.dev
   • Authorized Callback URL: https://mcp - strava - oauth.<your - subdomain>.workers.dev/callback

3. Set your production environment variables:

   wrangler secret put STRAVA_CLIENT_ID
   wrangler secret put STRAVA_CLIENT_SECRET
   

Development Environment

1. Go to Strava's developer console and create a new application.
2. Configure your application:
   • Application Name: e.g., MCP - Dev
   • Description: A short description like MCP Development App
   • Website URL: http://localhost:3000
   • Authorized Callback URL: http://localhost:3000/login/callback

💻 Usage Examples

Testing Your MCP Server

Using Inspector

1. Install and start Inspector.
2. Open Inspector's console.
3. Create a new MCP connection:

   mcp create connection --name test - connection --url http://localhost:5000
   

4. Start the connection:

   mcp start - connection test - connection
   

5. In Inspector, you should see logs and messages from the MCP server.

Using Claude Desktop

1. Open Claude Desktop and connect to your Cloudflare account.
2. Navigate to the Compute tab and select your MCP application.
3. In the right - hand console, you can interact with the MCP proxy:

   mcp create connection --name test - connection --url http://localhost:5000
   mcp start - connection test - connection
   

Development

Local Development

1. Clone the repository and install dependencies.
2. Start the development server:

   npm run dev
   

3. Open your browser and visit http://localhost:5000.

API Rate Limits

• Strava's free tier has a limit of 18,000 calls per hour.
• Exceeding the limit may result in requests being rejected or delayed.

🔧 Technical Details

Overview

The MCP server (powered by Cloudflare Workers) plays two roles:

• As an OAuth service provider for your MCP clients.
• As an OAuth client for Strava's OAuth service.

This project serves as a reference example, demonstrating how to integrate an OAuth provider into an MCP server deployed on Cloudflare using the [workers - oauth - provider library](https://github.com/cloudflare/workers - oauth - provider).

📄 Notes

⚠️ Important Note

• Ensure that all callback URLs are configured correctly and match exactly the settings in your Strava application.
• Regularly check API call limits to avoid exceeding the quota.
• Use HTTPS and configure SSL certificates in the production environment to ensure security.
• Manage sensitive information (such as client IDs and secrets) using environment variables.

By following the above steps, you can successfully deploy and run an MCP server supporting Strava login, and leverage Cloudflare's powerful features for expansion and optimization.