Caddie MCP vs Strava MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Caddie MCP vs Strava MCP
In-depth architectural comparison of the Caddie MCP and Strava MCP 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.
At a Glance & Executive Verdict
Caddie MCP
Sports · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Strava MCP
Sports · Local stdio
Quality: 65/100 (Great) | Auth: OAuth 2.0
Verdict Summary: Choose Caddie MCP if you need specialized Sports tools running via a local process. Choose Strava MCP if your workspace requires Sports integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Caddie MCP when:
You need dedicated capabilities in the Sports domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Caddie MCP is categorized under Sports and uses a local stdio subprocess. In contrast, Strava MCP belongs to Sports using local stdio subprocess. Select Caddie MCP when you need capabilities focused on sports and Strava MCP when you require tools for sports.
Broadie strokes gained per round: off-tee / approach / short game / putting, vs your handicap level or scratch
get_performance_stats
~40 PGA-style stats (driving, GIR by distance, scrambling, putting, scoring) with optional handicap benchmarks
get_handicap
WHS-style index, counting differentials, and trend
get_course_intel
Per-hole difficulty and usual tee club at one course
get_health_context
Sleep, HRV, Body Battery, readiness, and stress for a round's date
correlate_health_performance
"Do I score worse on bad sleep?" — paired data + honest correlation
+1 more tools listed on main page
Strava MCP Tools (24)
get-athlete-profile
Fetches the profile information for the authenticated athlete, including their unique numeric ID needed for other tools like get-athlete-stats.
get-athlete-stats
Fetches the activity statistics (recent, YTD, all-time) for a specific athlete using their ID. Requires the athleteId obtained from the get-athlete-profile tool.
get-activity-details
Fetches detailed information about a specific activity using its ID.
get-recent-activities
Fetches the most recent activities for the authenticated athlete.
list-athlete-clubs
Lists the clubs the authenticated athlete is a member of.
list-starred-segments
Lists the segments starred by the authenticated athlete.
get-segment
Fetches detailed information about a specific segment using its ID.
explore-segments
Searches for popular segments within a given geographical area.
star-segment
Stars or unstars a specific segment for the authenticated athlete.
get-segment-effort
Fetches detailed information about a specific segment effort using its ID.
list-segment-efforts
Lists the authenticated athlete's efforts on a specific segment, optionally filtering by date.
list-athlete-routes
Lists the routes created by the authenticated athlete, with pagination.