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

A Model Context Protocol (MCP) server with Strava OAuth integration, built on Cloudflare Workers. Enables secure authentication and tool access for

Local serverstdioGo

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

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. The model context protocol (mcp) server + strava oauth mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

This is a Model Context Protocol (MCP) server that supports remote MCP connections, with Strava OAuth built-in. It allows users to connect to your MCP server by signing in with their Strava account.

The MCP server (powered by Cloudflare Workers) serves two roles: - Acts as an OAuth Server for your MCP clients - Acts as an OAuth Client for Strava's OAuth services

Adding it to your client

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration

You will need 2 environment variables: STRAVA_CLIENT_ID, STRAVA_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the model context protocol (mcp) server + strava oauth mcp server does with a few real requests.

When to reach for it

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by kw510; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Model Context Protocol (MCP) Server + Strava OAuth's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

How to install the Model Context Protocol (MCP) Server + Strava OAuth MCP server

{
  "mcpServers": {
    "strava-mcp-kw510": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "STRAVA_CLIENT_ID": "your-value",
        "STRAVA_CLIENT_SECRET": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • A Strava account - A Cloudflare account - Node.js and npm installed - Wrangler CLI installed (npm install -g wrangler)
VariableDescriptionRequired
STRAVA_CLIENT_IDConfiguration value read at startup.Optional
STRAVA_CLIENT_SECRETCredential the server authenticates with.Yes

Frequently asked questions

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