Model Context Protocol (MCP) Server + Strava OAuth

Name: Model Context Protocol (MCP) Server + Strava OAuth
Author: kw510

@kw510

About Model Context Protocol (MCP) Server + Strava OAuth

A Model Context Protocol (MCP) server with Strava OAuth integration, built on Cloudflare Workers. Enables secure authentication and tool access for MCP clients like Claude and Cursor through Strava login. Perfect for developers looking to integrate Strava authentication with AI t

#oauth #authentication #mcp #strava #cloudflare-workers #model-context-protocol

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "strava-mcp-kw510": {
      "command": "npx",
      "args": [
        "@modelcontextprotocol/inspector@latest"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Model Context Protocol (MCP) Server + Strava OAuth?

This MCP server, deployed on Cloudflare Workers, supports remote MCP connections with built‑in Strava OAuth. It acts as an OAuth server for MCP clients and as an OAuth client for Strava, allowing users to sign in with their Strava account.

How to use Model Context Protocol (MCP) Server + Strava OAuth?

Clone the repository, install dependencies, set up Strava API credentials, create a Cloudflare KV namespace, and deploy with Wrangler. Test the server using the MCP Inspector or configure it in Claude Desktop via the mcp-remote command with the SSE endpoint.

Key features of Model Context Protocol (MCP) Server + Strava OAuth

OAuth 2.1 server implementation with token issuance and validation
Secure token storage in Cloudflare KV
Durable MCP for persistent state and authentication context
MCP Remote for client‑server communication over SSE
Strava OAuth integration as an OAuth client
Deployed and managed via Cloudflare Workers

Use cases of Model Context Protocol (MCP) Server + Strava OAuth

Allow AI assistants to access authenticated user Strava data via MCP
Build custom tools that interact with Strava using a user’s OAuth tokens
Demonstrate an MCP server with a real‑world OAuth provider integration
Enable remote MCP connections with secure, server‑managed OAuth flows

FAQ from Model Context Protocol (MCP) Server + Strava OAuth

What are the prerequisites?

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

How do I set up Strava API credentials for production?

Create a new application in Strava’s API settings, configure the callback domain and URL to point to your deployed Workers subdomain, and store the client ID and secret as Cloudflare secrets.

What are the Strava API rate limits?

200 requests every 15 minutes and 2,000 requests per day.

Where are tokens stored?

Tokens are securely stored in the Cloudflare KV namespace configured for OAuth.

How can I test the server locally?

Run wrangler dev to start the development server at http://localhost:8788 and use a separate Strava application with callback domain localhost.

Comments

More Developer Tools MCP servers

Huoshan Test

volcengine

2.4K

DevDocs by CyberAGI 🚀

cyberagiinc

Completely free, private, UI based Tech Documentation MCP server. Designed for coders and software developers in mind. Easily integrate into Cursor, Windsurf, Cline, Roo Code, Claude Desktop App

2.1K