Volleyball API
DocumentationLiveCoveragePricingMCPStatusSign inGet a free key

DocumentationStart here

Volleyball MCP server

MCP for AI agents

An MCP server at https://api.volleyballapi.com/mcp. Every endpoint is a tool with the same parameters, plans and limits, so an AI agent can look up scores, rallies, lineups and players in plain conversation.

Connecting

The server speaks MCP over HTTP: JSON-RPC messages sent with POST to https://api.volleyballapi.com/mcp, each answered on the same request. Send your API key the way the API takes it, in Authorization: Bearer or X-API-Key. Listing the tools needs no key; calling one does.

# Claude Code
claude mcp add --transport http volleyball https://api.volleyballapi.com/mcp \
  --header "Authorization: Bearer vba_your_key"

The tools

21 tools, one an endpoint, named after its page here. Each takes the endpoint's parameters as arguments, and ids in the same mt_, cp_, tm_ and pl_ form.

ToolWhat it returnsPlans
usageYour plan, your calls today and this month, your limits and the dates you can readEvery plan
liveEvery match being played now, with the running set scoresLive and Complete
results_yesterdayYesterday's finished matchesEvery plan
matchesMatches on a day or between two days, filtered by discipline, gender, status, competition or teamEvery plan
match_pointsEvery rally of every set: the score after it, who won it and who servedLive, Archive and Complete
match_playersPer-player figures for the match: points, serve, reception, attack and blockArchive and Complete
match_lineupsStarting six by court zone for every set, the players who came on, and both head coachesArchive and Complete
export_matchesEvery match between two days in one call, with sets, venue, officials and coaches (up to 184 days)Complete
export_lineupsEvery lineup between two days in one call: starting six by zone, players who came on, coaches (up to 92 days)Complete
export_pointsEvery rally of every match between two days in one call (up to 14 days)Complete
matchOne match: teams, result, every set, duration, venue, spectators and refereesEvery plan
competitionsCompetitions, newest first, filtered by discipline, gender, season or nameEvery plan
competition_matchesA competition's matchesEvery plan
competition_standingsLeague tables for a competition, one per pool, worked out from its resultsEvery plan
competitionOne competition, with its dates and match countEvery plan
teamsTeams and beach pairs, found by nameEvery plan
team_matchesA team's matches, newest firstEvery plan
teamOne team: its name, kind, federation and playersEvery plan
playersPlayers, found by nameEvery plan
playerOne player, the teams they have played for and their career, competition by competitionEvery plan
head_to_headEvery meeting of two teams, with the record between themLive, Archive and Complete

Answers and limits

A tool answers with the same JSON the endpoint gives, as text. An error from the API comes back as a tool error carrying the API's error object, so the agent can read what to change. Every tool call is one API call: it counts against your plan, its rate limit and its quota exactly as the REST call does.

Use with Claude and agents

The agent skill teaches Claude, Cursor and other agents how to use the Volleyball API: getting a key, the calls that answer common questions, the limits and the errors. Pair it with the MCP server so the agent can make the calls itself.

Download SKILL.md

Save it as ~/.claude/skills/volleyballapi/SKILL.md, or upload it as a skill in Claude's settings. Agents also find it at /.well-known/agent-skills/index.json.