Strava MCP vs UFCalendar Fight API

In-depth architectural comparison of the Strava MCP and UFCalendar Fight API MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Strava MCP when:

• You need dedicated capabilities in the Sports domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: OAuth 2.0 (BYOK (Pay Provider Direct)).
• You have access to required keys: STRAVA_CLIENT_ID, STRAVA_CLIENT_SECRET.
• Primary tools included: get-athlete-profile, get-athlete-stats, get-activity-details.

Explore Strava MCP Details

Choose UFCalendar Fight API when:

• You need dedicated capabilities in the Sports domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore UFCalendar Fight API Details

Feature & Specification Comparison

Specification	Strava MCP r-huijts Sports	UFCalendar Fight API Sports
Summary	A Model Context Protocol (MCP) server that connects to Strava API, providing tools to access Strava data through LLMs	MMA fight data: UFC, PFL, OKTAGON, BKFC, RIZIN events, results, stats, rankings, judges scorecards.
Category & Scope	Sports	Sports

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "r-huijts-strava-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@r-huijts/strava-mcp-server"
      ],
      "env": {
        "STRAVA_CLIENT_ID": "YOUR_STRAVA_CLIENT_ID_HERE",
        "STRAVA_CLIENT_SECRET": "YOUR_STRAVA_CLIENT_SECRET_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "ufcalendar-fight-api": {
      "url": "https://api.ufcalendar.com/mcp"
    }
  }
}

Related MCP Server Comparisons