Ladderboard — round-robin ladders and match scores for small clubs

Official5 tools

by ladder

Round-robin ladders and match scores for small clubs. Players join by QR poster; no app, no account.

The Model Context Protocol (MCP) server app.rowb.ladder/board supports round-robin ladders and match scores for small clubs. Players join via a QR poster workflow, and the system is described as requiring no app and no account.

🛠️ Key Features

Round-robin ladders
Match score tracking
Player join via QR poster
No app required
No account required

🚀 Use Cases

Organizing small club competitions
Recording match results in a round-robin format
On-site player participation using QR poster access

⚡ Developer Benefits

QR-based entry removes account/session setup from the described flow
Straightforward ladder and score management focus

⚠️ Limitations

Based on the provided description only: no app and no account implies limited user access paths to the QR poster method

Captured live from the server via tools/list.

create_ladder

Create or update the club ladder: club name and sport. Returns the join URL (the poster target) that players scan.

Parameters2

club	string	required
sport	string	optional

Raw schema

{
  "type": "object",
  "properties": {
    "club": {
      "type": "string"
    },
    "sport": {
      "type": "string"
    }
  },
  "required": [
    "club"
  ]
}

add_player

Register one player by name. Returns a 6-character code and a personal URL so the player can be identified at the courts without an account.

Parameters1

name

string

required

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    }
  },
  "required": [
    "name"
  ]
}

record_match

Record a finished match result. Identify players by name, numeric id, or 6-character code. Give the set score (sets_a, sets_b) and optionally the games.

Parameters7

player_a	string	required
player_b	string	required
sets_a	integer	required
sets_b	integer	required
games_a	integer	optional
games_b	integer	optional
round	integer	optional

Raw schema

{
  "type": "object",
  "properties": {
    "player_a": {
      "type": "string"
    },
    "player_b": {
      "type": "string"
    },
    "sets_a": {
      "type": "integer"
    },
    "sets_b": {
      "type": "integer"
    },
    "games_a": {
      "type": "integer"
    },
    "games_b": {
      "type": "integer"
    },
    "round": {
      "type": "integer"
    }
  },
  "required": [
    "player_a",
    "player_b",
    "sets_a",
    "sets_b"
  ]
}

schedule_match

Put a match on the calendar before it is played. It appears as a pending card in the standings output.

Parameters3

player_a	string	required
player_b	string	required
round	integer	optional

Raw schema

{
  "type": "object",
  "properties": {
    "player_a": {
      "type": "string"
    },
    "player_b": {
      "type": "string"
    },
    "round": {
      "type": "integer"
    }
  },
  "required": [
    "player_a",
    "player_b"
  ]
}

get_standings

The current table (rank, wins, losses, set percentage) plus the single most useful match to play next. Standings are computed with a fixed rule order, so the same results always give the same table.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

Install

Tools (5)

create_ladderadd_playerrecord_matchschedule_matchget_standings

Remote endpoint

Streamable HTTP

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

url

https://ladder.rowb.app/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "board": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://ladder.rowb.app/mcp"
      ]
    }
  }
}

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

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

create_ladder

add_player

record_match

schedule_match

get_standings

Install

Remote endpoint

Related servers