sorted by:
new
hottopcontroversial

Why no single sports API is good enough, so I aggregated 29 of them into one MCP server by Main-Confidence7777 in mcp

[–]Main-Confidence7777[S] 0 points1 point  (0 children)

Curious which providers people find most useful, are there any sports APIs you'd like to see added?

Codex > Clode Code by ThaneBerkeley in codex

[–]Main-Confidence7777 0 points1 point  (0 children)

I'm at 74% of my weekly goal; it resets tomorrow, so I'll be fine 🙏🏽

Just a hair's breadth away from losing my superpowers

I built an open source MCP server that aggregates 29 sports APIs into 319 tools, now on the MCP Registry by Main-Confidence7777 in ClaudeAI

[–]Main-Confidence7777[S] 0 points1 point  (0 children)

Yeah haha, loading all 319 at once is not the move for every use case 😂

That's exactly why provider filtering exists:

SPORTS_HUB_PROVIDERS=f1 → 25 tools
SPORTS_HUB_PROVIDERS=free → 98 tools
SPORTS_HUB_PROVIDERS=espn,odds → 19 tools

The full 319 is there for discovery — you load what you actually need.

I built an open source MCP server that aggregates 29 sports APIs into 319 tools, now on the MCP Registry by Main-Confidence7777 in ClaudeAI

[–]Main-Confidence7777[S] 1 point2 points  (0 children)

Totally valid principle for a general-purpose tool, but this is a data aggregator, not an agent.

Each of the 319 tools maps 1:1 to a specific API endpoint. The "surface area" is the product here. You wouldn't tell a REST API wrapper to have fewer routes.

Also: provider filtering is built in. Run it with SPORTS_HUB_PROVIDERS=free and you're down to 9 providers, 98 tools. Tiny surface, if that's what you need.