INDIVIDUAL MCP TOOL
get_player
One charted player's scouting report, found by name: serve and return points won against an average opponent, shot ratings per 100 shots (direction choice, shot selection, execution, long rallies, points left on the table) with tour percentiles, first-serve direction habits per court including on break points, how exploitable the serve is and the optimal mix, the shots they hurt opponents with most and the shots they are most exposed to, best-equipped opponents, stylistically similar players and recent charted matches.
LIVE ENDPOINT
https://bigballi.com/RallyIQ/mcp
Connect to this endpoint to inspect the live schema for get_player and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.rallyiq]
url = "https://bigballi.com/RallyIQ/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"rallyiq": {
"type": "http",
"url": "https://bigballi.com/RallyIQ/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: rallyiq
Remote MCP URL: https://bigballi.com/RallyIQ/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"rallyiq": {
"url": "https://bigballi.com/RallyIQ/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"rallyiq": {
"type": "http",
"url": "https://bigballi.com/RallyIQ/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "rallyiq",
"transport": "streamable-http",
"url": "https://bigballi.com/RallyIQ/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
get_game_plan— A scouting game plan for one player against an opponent, from 11,822 shot-by-shot charted ATP and WTA matches: the match forecast with a 90% range (same tour only), where to serve first serves on each court against this returner and the optimal mix, which returns work best against this server, the rally shots to favour and to avoid, what the opponent tends to serve, career shot ratings side by side, style compatibility and the charted head-to-heads.explain_match— Why a charted match went the way it did: points won, and each player's gain or loss against expectation split into direction choice, shot selection and execution, by stroke and by set, the loser's biggest leaks and the points each player left on the table by not choosing the best-value direction.get_leaders— Top 10 ATP or WTA players on one tactical measure: direction_choice: Picks the more valuable direction for the stroke being hit (per 100 shots, opponent-adjusted).