- 6 toolsread-only, over live platform data
- 2 modesnatural-language answers or structured JSON
- In developmentbeing integrated into the Pickleball.com experience
The challenge
Everything a player wants to know, tournaments open for registration, clubs nearby, team and ladder leagues, player ratings, already exists in the platform API, but only if you know which filters to set. People ask in sentences; the API answers parameters.
What we built
An MCP server exposing six read-only tools, tournaments, players, clubs, team leagues, ladder leagues and a support FAQ. A question is routed to the right tool, its parameters extracted from the sentence (rating, format, gender, location, status), live data queried, and the answer streamed back as natural language.
A second mode returns the same result as structured JSON, so product surfaces can render cards instead of prose. Scoped authentication with cached tokens, location awareness and read-only access are built in.
The outcome
One server that answers a person in chat and an application over an API, and a reusable pattern for making any platform AI-addressable.
- Model Context Protocol
- AI agents
- Tool calling
- Streaming SSE
- Live platform data
- Read-only by design