RallyIQ

Official4 tools

by BigBalli

Tennis game plans, scouting reports and match breakdowns from shot-by-shot charted matches.

com.bigballi/rallyiq (MCP Server)

This MCP server provides access to tennis game plans, scouting reports, and match breakdowns derived from shot-by-shot charted matches. The catalog entry for the server identifies it by the slug com-bigballi-rallyiq and describes its content as focused on match analysis materials.

🛠️ Key Features

Tennis game plans
Scouting reports
Match breakdowns
Shot-by-shot charted match data

🚀 Use Cases

Reference tennis game plans for specific matchups
Review scouting reports to inform preparation
Analyze match breakdowns based on shot-by-shot charting

⚡ Developer Benefits

Structured access to match-analysis content types (plans, scouting, breakdowns)
Developer-friendly categorization aligned to shot-by-shot charted sources

⚠️ Limitations

No tool count or additional operational details were provided in the available server data

Captured live from the server via tools/list.

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. Optionally for one surface.

Parameters3

player	string	required	The player the plan is for, e.g. "Jannik Sinner", "Swiatek", "Alcaraz". Misspellings and surnames alone are fine.
opponent	string	required	The opponent, e.g. "Jannik Sinner", "Swiatek", "Alcaraz". Misspellings and surnames alone are fine.
surface	string	optional	Court surface for the forecast and rally plan (default all).

Raw schema

{
  "type": "object",
  "properties": {
    "player": {
      "type": "string",
      "maxLength": 80,
      "description": "The player the plan is for, e.g. \"Jannik Sinner\", \"Swiatek\", \"Alcaraz\". Misspellings and surnames alone are fine."
    },
    "opponent": {
      "type": "string",
      "maxLength": 80,
      "description": "The opponent, e.g. \"Jannik Sinner\", \"Swiatek\", \"Alcaraz\". Misspellings and surnames alone are fine."
    },
    "surface": {
      "type": "string",
      "enum": [
        "all",
        "hard",
        "clay",
        "grass"
      ],
      "description": "Court surface for the forecast and rally plan (default all)."
    }
  },
  "required": [
    "player",
    "opponent"
  ],
  "additionalProperties": false
}

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. When the name matches several players it returns the best match and lists the others.

Parameters2

name	string	required	The player, e.g. "Jannik Sinner", "Swiatek", "Alcaraz". Misspellings and surnames alone are fine.
tour	string	optional	Restrict the name search to one tour when a surname is shared (e.g. Williams).

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 80,
      "description": "The player, e.g. \"Jannik Sinner\", \"Swiatek\", \"Alcaraz\". Misspellings and surnames alone are fine."
    },
    "tour": {
      "type": "string",
      "enum": [
        "atp",
        "wta"
      ],
      "description": "Restrict the name search to one tour when a surname is shared (e.g. Williams)."
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false
}

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. Finds the most recent charted match for a player, narrowed by opponent, tournament or year, and lists other matching matches.

Parameters4

player	string	required	A player in the match, e.g. "Jannik Sinner", "Swiatek", "Alcaraz". Misspellings and surnames alone are fine.
opponent	string	optional	The other player (optional), e.g. "Jannik Sinner", "Swiatek", "Alcaraz". Misspellings and surnames alone are fine.
tournament	string	optional	Words from the tournament name, e.g. "Wimbledon", "Roland Garros", "Indian Wells".
year	integer	optional	Season of the match.

Raw schema

{
  "type": "object",
  "properties": {
    "player": {
      "type": "string",
      "maxLength": 80,
      "description": "A player in the match, e.g. \"Jannik Sinner\", \"Swiatek\", \"Alcaraz\". Misspellings and surnames alone are fine."
    },
    "opponent": {
      "type": "string",
      "maxLength": 80,
      "description": "The other player (optional), e.g. \"Jannik Sinner\", \"Swiatek\", \"Alcaraz\". Misspellings and surnames alone are fine."
    },
    "tournament": {
      "type": "string",
      "maxLength": 60,
      "description": "Words from the tournament name, e.g. \"Wimbledon\", \"Roland Garros\", \"Indian Wells\"."
    },
    "year": {
      "type": "integer",
      "minimum": 1960,
      "maximum": 2100,
      "description": "Season of the match."
    }
  },
  "required": [
    "player"
  ],
  "additionalProperties": false
}

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). execution: Gets more out of a shot than the same choice usually yields (per 100 shots, opponent-adjusted). shot_selection: Chooses strokes worth more than the position average; partly reflects the ball they were given (per 100 shots, opponent-adjusted). fewest_points_left: Smallest gap per 100 shots between the direction chosen and the best-value direction for that stroke. most_exploitable_serve: Points per 100 first serves an optimal direction mix would win over the current one, allowing for returners reading a habit. serve_off_equilibrium: First-serve directions that win at clearly different rates (p < 0.01): usage-weighted gap per 100 first serves and the direction to use more. long_rallies_hold_up: Execution from the ninth shot of a rally on, minus the player's own earlier-rally execution, per 100 shots (ATP only). long_rallies_fade: The same long-rally measure, most fading first (ATP only). adaptability: Moves the first-serve mix toward what has been winning in earlier sets, per 100 first serves. A weak habit, not a proven gain. adapts_fastest: The same, every two to three service games, per 100 first serves. Players need at least 5,000 modelled shots.

Parameters3

board	string	required	Which leaderboard.
tour	string	optional	atp (default) or wta.
scope	string	optional	active: charted in the last three seasons (default); all_eras: every era.

Raw schema

{
  "type": "object",
  "properties": {
    "board": {
      "type": "string",
      "enum": [
        "direction_choice",
        "execution",
        "shot_selection",
        "fewest_points_left",
        "most_exploitable_serve",
        "serve_off_equilibrium",
        "long_rallies_hold_up",
        "long_rallies_fade",
        "adaptability",
        "adapts_fastest"
      ],
      "description": "Which leaderboard."
    },
    "tour": {
      "type": "string",
      "enum": [
        "atp",
        "wta"
      ],
      "description": "atp (default) or wta."
    },
    "scope": {
      "type": "string",
      "enum": [
        "active",
        "all_eras"
      ],
      "description": "active: charted in the last three seasons (default); all_eras: every era."
    }
  },
  "required": [
    "board"
  ],
  "additionalProperties": false
}

README.md4 KBView on GitHub

RallyIQ for Claude and other MCP clients

RallyIQ

Ask an AI assistant how a tennis player should play an opponent and get an answer from shot-by-shot match data instead of memory: where to serve on each court, which returns work against that server, which rally patterns to favour and avoid, who is likely to win, and why a match turned.

This repository holds:

the connection details for the RallyIQ remote MCP server at https://bigballi.com/RallyIQ/mcp,
a Claude plugin that adds that server plus a tennis-scouting skill, which teaches Claude how to read the numbers.

The server is run by RallyIQ, which models more than 11,000 ATP and WTA matches charted shot by shot by volunteers for the Match Charting Project. Each shot is valued by how much it changed its hitter's chance of winning the point. How it works: method.

What you can ask

"Give me a game plan for Sinner against Alcaraz on clay."
"Where does Iga Swiatek serve on break points, and is her serve easy to read?"
"What are Coco Gauff's biggest weaknesses, and who is best equipped to exploit them?"
"Why did Djokovic lose the 2023 Wimbledon final?"
"Which active WTA players choose their shot direction best?"

Tools

All tools are read-only (readOnlyHint: true) and need no account.

Tool	What it answers
`get_game_plan`	One player against an opponent, optionally on one surface: the match forecast with a 90% range, first-serve directions and the optimal mix on each court against that returner, the opponent's serve, the best returns against that server, rally shots to favour and avoid, career shot ratings side by side and the charted head-to-heads.
`get_player`	One player's scouting report: serve and return points won against an average opponent, shot ratings per 100 shots with tour percentiles, first-serve habits including on break points, how exploitable the serve is, the shots they hurt opponents with and the shots they are most exposed to, and similar players.
`explain_match`	Why a charted match went the way it did: each player's points against expectation split into direction choice, shot selection and execution, by stroke and by set, and the points each left on the table.
`get_leaders`	The top 10 ATP or WTA players on one of ten tactical measures, active or across eras.

Every value comes with a 90% margin and a link to the full page on RallyIQ.

Setup

Claude (claude.ai, Desktop, mobile)

Settings → Connectors → Add custom connector, then paste https://bigballi.com/RallyIQ/mcp. No sign-in is needed.

Claude Code

Install the plugin, which adds the server and the tennis-scouting skill:

code

/plugin marketplace add BigBalli/rallyiq-mcp
/plugin install rallyiq@rallyiq

Or add only the server:

code

claude mcp add --transport http rallyiq https://bigballi.com/RallyIQ/mcp

Other MCP clients

Any client that supports remote MCP servers over Streamable HTTP can use https://bigballi.com/RallyIQ/mcp with no credentials. The server speaks protocol versions 2026-07-28, 2025-11-25, 2025-06-18 and 2025-03-26 and answers with JSON (no SSE, no sessions).

Privacy

The server receives the tool name and its arguments (for example two player names and a surface), uses them to answer, and does not store them. It never sees your conversation or your account. Full policy: bigballi.com/RallyIQ/privacy.

Support

Email g@bigballi.com, or see bigballi.com/RallyIQ/connect.

License

The contents of this repository are released under the MIT License. The data served by the RallyIQ MCP server is not part of this repository: it derives from the Match Charting Project and is licensed CC BY-NC-SA 4.0, which requires crediting the Match Charting Project wherever it is used.

Install

Tools (4)

get_game_planget_playerexplain_matchget_leaders

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://bigballi.com/RallyIQ/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "rallyiq": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://bigballi.com/RallyIQ/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

com.bigballi/rallyiq (MCP Server)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

get_game_plan

get_player

explain_match

get_leaders

RallyIQ for Claude and other MCP clients

What you can ask

Tools

Setup

Claude (claude.ai, Desktop, mobile)

Claude Code

Other MCP clients

Privacy

Support

License

Install

Remote endpoint

Related servers