Ride with GPS API vs Strava MCP Connector + API

Ride with GPS API 24

Read with the hosted lines. No status page, since status.ridewithgps.com answers 301 to the home page and the docs link none (0). No readable incident history (5). The API terms of 11 September 2026 say no fixed request limits currently apply and ask for caching, webhooks and backing off, so there are no numbers to publish (5 of 15). No 429 is documented in the docs or the OpenAPI file; the terms ask clients to back off on failures, uploads run as tasks to poll, and no idempotency key exists for the 30 write operations (4 of 15). No SLA (0). v1 is the current and only version with no beta label (10). 0 + 5 + 5 + 4 + 0 + 10 = 24.

Strava MCP Connector + API 63

Read with the hosted lines on the MCP Connector, the surface Strava sanctions for an assistant, with the V3 API where the connector publishes nothing. status.strava.com on Atlassian Statuspage lists Mobile applications, Strava.com, API, Upload, AWS and MCP Connector components with a history feed (20). From 4 August to 3 November 2026 the feed has 15 resolved incidents. None touches the MCP Connector; the API component had Beacon failures for 48 minutes on 23 October; activity uploads were degraded for 3 hours 7 minutes on 27 September with the mobile app unavailable for most users, and Garmin uploads were delayed twice. For the graded surface that reads as minor incidents only (20). API limits are published with numbers (200 per 15 minutes and 2,000 a day, 100 and 1,000 for reads, doubled after the self-service upgrade); the MCP article says limits per minute and per day exist and gives none (8 of 15). The API returns 429 with a JSON error and X-RateLimit-Usage headers and asks callers to throttle, with no Retry-After, and the connector is read-only, so retries are safe; nothing on MCP overload (5 of 15). No SLA (0). The connector launched on 1 June 2026 and carries no beta label (10). 20 + 20 + 8 + 5 + 0 + 10 = 63.

Ride with GPS API 30

Read with the hosted rubric. No x402, MPP or L402 (0). The API is free under the terms and the plan prices are stated in llms.txt and the App Store listing, but the pricing page shows no figures to our reader and organisation accounts, which the member, event, experience and point-of-interest endpoints need, are priced by email (10 of 20). A free Starter account and a free API client with no card (20). A person signs up and creates the API client in a browser, and basic auth tokens need the account password (0). 0 + 10 + 20 + 0 = 30.

Strava MCP Connector + API 0

Read with the hosted rubric. No x402, MPP or L402 (0). A subscription is required and the FAQ says it carries no extra API fee, but the price is on www.strava.com, which robots.txt disallows for our reader, so the pricing line is scored absent and named in openQuestions (0 of 20). No free tier for the connector or for Standard Tier apps, and any subscription trial sits on the unread host (0 of 20). A person subscribes and completes OAuth in a browser (0). 0 + 0 + 0 + 0 = 0.

Ride with GPS API 72

Public OpenAPI 3.0.1 file with 34 paths, 61 operations and 41 schemas (25). ridewithgps.com/llms.txt describes the product and plans but links no Markdown docs, and the documentation is HTML (5 of 10). Operation descriptions say which endpoints are organisation-only, that uploads and package builds return a task to poll, how experience codes replace each other and that deleting a member keeps their account; little on when not to use an operation (14 of 20). 18 enums, required fields and defaults in the file, but the Error schema is an array of strings (10 of 15). One example in the OpenAPI file, request and pagination examples on the docs pages, and a table of HTTP codes with the errors array shape (8 of 15). One version in the path, a rule that only incompatible changes create a new version, and a dated change log back to January 2025 (15). 25 + 5 + 14 + 10 + 8 + 15 = 72.

Strava MCP Connector + API 50

A public Swagger 2.0 file describes the V3 API (29 paths, 31 operations, 7 OAuth scopes). The MCP tool definitions are only visible after OAuth, which we did not run, so the contract line is scored on the API half (15 of 25). No llms.txt on developers.strava.com (404) and no Markdown docs (0). The support article names the data the connector reads (activity history, fitness trends, cross-sport insights, gear, best efforts, weather, streaks) and the Swagger descriptions state each operation's purpose and scope; no when-not-to-use guidance and no tool descriptions read (6 of 20). The Swagger file has enums for upload data_type, stream keys and explore activity_type and marks required parameters; one PUT /athlete parameter is declared in the path with no placeholder; MCP inputs unread (6 of 15). Most 200 responses carry examples, errors return a Fault object, 429 is not in the file, and the rate-limits page documents the 429 body (8 of 15). A dated changelog on developers.strava.com with removals announced three months ahead (15). 15 + 0 + 6 + 6 + 8 + 15 = 50.

Ride with GPS API 60

Read for a closed service. The newest change log entry is 14 October 2026 (30). Five dated entries since 4 August 2026, on 10 August, 3 September, 11 September, 6 October and 14 October (20). A dated change log, developers@ridewithgps.com and a Zendesk help centre that answered 403 to our reader; replies were not tested (10 of 15). No official SDK and no entry in the official MCP registry (0 of 15). No package or CI to judge (0 of 10). 30 + 20 + 10 + 0 + 0 = 60.

Strava MCP Connector + API 40

Read for a closed service. Gemini support for the connector arrived on 28 October 2026, and the API changelog's newest entry is 1 September 2026 (30). In the 90 days to 3 November, dated changes are the 1 September endpoint removals and the 28 October Gemini release; the 18 September FAQ is a document, not a change, so three are not established (0 of 20). A dated changelog, a Developer FAQ on the Community Hub (closed to replies), a developer forum there and a support site (10 of 15). No entry in the official MCP registry under a strava.com namespace and no official SDKs, only Swagger Codegen (0 of 15). No package or CI to assess (0 of 10). 30 + 0 + 10 + 0 + 0 = 40.

Ride with GPS API 30

OAuth 2.0 authorisation code flow with one scope, user, and a revoke endpoint, but no PKCE, expiry or refresh token is documented; basic auth tokens are minted from the account email and password with no documented expiry or revocation; credentials travel in headers (18 of 30). No read-only scope, and the 30 write operations, including deletes of routes, events, members and experiences, need no confirmation (4 of 20). Route names, descriptions, event text and experience messages are user content with no guidance on treating them as untrusted (5 of 15). The API clients page lists clients and tokens; no call log is documented (3 of 15). /.well-known/security.txt returns 404, and no disclosure policy, bug bounty or certification was found (0 of 20). 18 + 4 + 5 + 3 + 0 = 30.

Strava MCP Connector + API 48

OAuth 2.0 with seven scopes, 6-hour access tokens, rotating refresh tokens that invalidate the previous one, and POST /oauth/revoke with Basic auth; the connector's consent is in the browser and revocable under My Apps. The token endpoint's parameter table lists client_secret, refresh_token and access_token as query parameters, a documented option that costs 10 (20 of 30). The connector is read-only and scoped to one account, and the API splits read, read_all and write scopes by resource; no confirmation step exists for activity:write (18 of 20). Activity titles, descriptions, comments and club posts are user text the connector returns, with no guidance on treating them as untrusted (5 of 15). My Apps lists connected apps for revocation and the API dashboard shows rate-limit usage; no per-call log (5 of 15). security.txt, a disclosure policy, a bug bounty and certifications would sit on www.strava.com, which our reader could not fetch, and the support article's "security and quality guardrails" is a claim; scored absent and named in openQuestions (0 of 20). 20 + 18 + 5 + 5 + 0 = 48.

Ride with GPS API 57

No field selection; polylines and track files sit on separate endpoints and page_size runs from 20 to 200 (12 of 25). page and page_size with meta.pagination, filters for name, visibility, distance, elevation gain, archived and stationary, and privacy_code for non-public items (20). Errors carry HTTP codes and an errors array of messages with no codes to branch on (10 of 20). Reads are safe to repeat and package builds return 409 while one runs, but no idempotency key covers creates, and deletes are not confirmed (8 of 20). Two headers and a .json suffix are all a request needs, with no official SDK (7 of 15). 12 + 20 + 10 + 8 + 7 = 57.

Strava MCP Connector + API 49

The connector's tool count and definition sizes are not public, so context cost is scored as unknown (10 of 25). The API pages with page and per_page up to 200, before and after timestamps on activities and a cursor on comments; stream keys select channels; whether the MCP tools size their output is unread (12 of 20). API errors return a Fault object with a message and a 429 JSON error, with no error codes list; MCP errors unread (8 of 20). The connector is read-only, so every call is safe to repeat, and the API's reads are too; no idempotency key on uploads and no annotations read (12 of 20). Setup is one claude mcp add command plus browser consent; the API has sensible defaults but no official SDKs, only Swagger Codegen (7 of 15). 10 + 12 + 8 + 12 + 7 = 49.