I’ve been watching the sports-technology landscape for years now, and I have to tell you what’s happening with infrastructure discovery is fascinating. Not in a “let me check my email” kind of way, but in a “this is actually changing how we build things” kind of way.
Let me tell you about Developers Locker Room and why I created it a little less than a year ago..
It’s a directory, and I know what you’re thinking, because I thought it too: another directory? But here’s the thing: this one’s different. It’s become the discovery layer for sports-tech infrastructure, and the numbers from their latest update tell a story that’s worth paying attention to.
In what was my third update in a week, we just added another 84 new resources to our catalog.
That might not sound like much until you realize we’re now tracking 1,828 different APIs, MCP servers, datasets, and tools across the entire sports-technology stack. And here’s what caught my eye: 63.3% of everything we track now supports Model Context Protocol.
That’s the agent-oriented access layer that’s quietly becoming the new way we interact with data.
Think about that for a moment. We’re watching a fundamental shift in how developers access sports data, and it’s happening right in front of us.
The MCP Revolution (And Why It Matters)
I remember when APIs were the hot new thing. When getting structured data from a service felt revolutionary. Now we’re moving beyond that. MCP servers essentially give AI agents the ability to interact with sports data directly, without developers having to build custom integrations for every use case.
Developers Locker Room now lists 967 dedicated MCP servers. That’s not a typo. Nearly a thousand different ways for AI agents to access sports infrastructure ranging from Garmin training data to golf handicaps to live football fixtures. The catalog grew by 67 MCP servers in this latest update alone, and the momentum feels like early blogging platforms or the first wave of mobile apps.
I’ve seen this movie before. When technology makes something dramatically easier, the floodgates open.
Where the Growth Is Happening
The distribution of these additions tells its own story. Wearables and health tech led the pack with 15 new resources. This makes perfect sense when you think about it. We’re all walking around with sensors on our wrists, tracking everything from heart rate variability to sleep patterns to training load. That data needs infrastructure, and developers are building it.
Multi-sport platforms added 13 resources. Golf, yes, golf, added 10. There’s something delightful about golf being a hotbed of sports-tech innovation, but when you consider the sport’s obsession with data (every shot tracked, every course mapped, handicaps calculated to absurd precision), it makes perfect sense.
Soccer added seven. American football added five. Even niche categories like disc golf are getting their own dedicated infrastructure.
What we’re witnessing is the democratization of sports data infrastructure. You don’t need to be ESPN or a major betting operator anymore to access sophisticated sports data; you just need to know where to look.
The Details Matter (Even When They’re Boring)
Here’s where I appreciate the rigor: this update added 84 resources without changing a single field in the 1,744 existing records. No timestamps altered. No categories reassigned. No retroactive “improvements” that make historical comparisons impossible.
That might sound like inside baseball, and it is, but it’s the kind of editorial discipline that makes a directory actually useful over time. When four candidate resources were rejected to prevent duplicates, when package descriptions were narrowed to only what’s actually implemented rather than what’s advertised, when verification happened even for packages with missing GitHub repositories… that’s the unglamorous work that separates signal from noise.
I’ve watched too many directories become junkyards of abandoned projects and broken links. The fact that someone’s actually maintaining this thing, with clear methodology and transparent decision-making, is worth noting.
What This Means for Builders
If you’re building anything in sports tech right now ā and I mean anything, from a fantasy app to a venue management system to an AI agent that can analyze game footage ā this is your starting point. Not your ending point, mind you. The directory explicitly doesn’t verify uptime, authentication, performance, or production readiness. You still have to do that work yourself.
But it gives you the map. And in a landscape this fragmented, with infrastructure scattered across hundreds of providers and thousands of endpoints, having a map is the difference between spending three weeks researching options and spending three hours.
The catalog now spans 26 categories and 28 sport groups. There are APIs for ticket markets, MCP servers for Strava data, datasets for baseball statistics, and tools for calculating expected goals in soccer. Someone even built an MCP server just for sports rules. Another one specifically for PDGA disc golf data.
This is what happens when infrastructure becomes accessible. People build things you’d never think to build yourself.
The Bigger Picture
I keep coming back to this: we’re in the early innings of AI agents interacting with sports data. The fact that nearly two-thirds of sports-tech infrastructure now supports agent-oriented access suggests we’re past the experimental phase and into the “this is actually happening” phase.
Fast forward a few years, maybe sooner, and the way we consume sports information will look completely different. Instead of opening five different apps to check scores, read analysis, update your fantasy lineup, and watch highlights, you’ll just… ask. And some agent, somewhere, will orchestrate access across all this infrastructure to give you exactly what you want.
That future requires a discovery layer. It requires someone to catalog what exists, verify what works, and maintain the map as the landscape evolves. Developers Locker Room is building that layer, one update at a time.
Is it perfect? No. Is it comprehensive? Not yet. But it’s real, it’s growing, and it’s solving a problem that needed solving.
And honestly? That’s more than most directories can say.
The sports-tech infrastructure landscape just got a little more navigable. For builders, that’s not a small thing. It’s everything.