Ledgerfc vs Strava MCP
A side-by-side look at the Ledgerfc and Strava MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ledgerfc for sports work as a local process; choose Strava MCP for sports as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ledgerfc when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_track_record, get_predictions, get_arbs.
Choose Strava MCP when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
get-athlete-profile, get-athlete-stats, get-activity-details.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Sports | Sports |
| Quality signal | 59/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 500 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 13 | 24 |
| Full listing | View Ledgerfc | View Strava MCP |
Tools & capabilities
Ledgerfc tools 13
get_track_recordHonest settled record + high-confidence subset + CLV.get_predictionsUpcoming predictions with probabilities and model-vs-market edge.get_arbsPRO: recently detected live arbitrage opportunities. Needs a Pro key, via an Authorization: Bearer header (preferred) or the api_key argument.get_value_betsPRO: upcoming picks with positive model-vs-market edge. Needs a Pro key, via an Authorization: Bearer header (preferred) or the api_key argument.searchSearch upcoming match predictions. Returns {id,title,url} results; use fetch(id) for the full prediction.fetchFetch the full prediction document for a search result id.submit_predictionSubmit a prediction to be scored by CLV (shadow/points).get_leaderboardContributors ranked by CLV (reputation points, not cash).get_contributor_scoreA contributor's CLV record.place_betPlace a paper bet against our agent's prediction (points only).get_balanceYour paper-points balance (not cash).get_my_betsYour paper bets, newest first.- +1 more on the listing page
Strava MCP tools 24
get-athlete-profileFetches the profile information for the authenticated athlete, including their unique numeric ID needed for other tools like get-athlete-stats.get-athlete-statsFetches 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-detailsFetches detailed information about a specific activity using its ID.get-recent-activitiesFetches the most recent activities for the authenticated athlete.list-athlete-clubsLists the clubs the authenticated athlete is a member of.list-starred-segmentsLists the segments starred by the authenticated athlete.get-segmentFetches detailed information about a specific segment using its ID.explore-segmentsSearches for popular segments within a given geographical area.star-segmentStars or unstars a specific segment for the authenticated athlete.get-segment-effortFetches detailed information about a specific segment effort using its ID.list-segment-effortsLists the authenticated athlete's efforts on a specific segment, optionally filtering by date.list-athlete-routesLists the routes created by the authenticated athlete, with pagination.- +12 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Ledgerfc
{
"mcpServers": {
"ledgerfc": {
"command": "npx",
"args": [
"-y",
"@inbin/ledgerfc-mcp"
]
}
}
}
Strava MCP
{
"mcpServers": {
"r-huijts-strava-mcp": {
"command": "npx",
"args": [
"-y",
"@r-huijts/strava-mcp-server"
]
}
}
}
Frequently asked questions
Ledgerfc is categorized under Sports and uses a local stdio subprocess. Strava MCP belongs to Sports and uses a local stdio subprocess. Pick Ledgerfc for sports work and Strava MCP for sports.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Ledgerfc has no declared pricing — check the project's own site. Strava MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ledgerfc and r-huijts-strava-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ledgerfc has a quality signal of 59/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Strava MCP has 67/100 (Great) with 2 views, 0 installs and 500 GitHub stars.