Squadcard

What the Squadcard MCP server does

The Squadcard MCP server connects an AI agent to Squadcard, an app for organising recurring football groups. It covers the main coordination tasks around a game: creating or joining a squad, setting the next match, collecting attendance responses, selecting balanced teams, recording the result, and retrieving the voting link.

It also provides standalone football utilities. An agent can split a supplied list of players into two teams while separating the keepers, generate round-robin fixtures for three to 16 teams, and suggest team names from a theme or word.

How it works

The service is available at https://squadcard.app/api/mcp over HTTP. Add that endpoint to an MCP client, then authenticate with Squadcard when the first tool is used. The browser-based sign-in associates the agent session with the signed-in person and allows account-specific actions such as listing squads or answering for the next game.

The workflow can cover an entire weekly match. An agent can create a squad and return its invite link, or join an existing squad from a supplied invite link. It can set the time and location, report who is in, maybe, or out, select teams from the confirmed players, record the score, and provide the link that opens voting. Squad and match lookup tools expose the relevant invite, game, turnout, teams, and score information.

Setup and configuration

For clients that accept JSON MCP configuration, add the remote HTTP server under the squadcard name:

{
  "mcpServers": {
    "squadcard": {
      "type": "http",
      "url": "https://squadcard.app/api/mcp"
    }
  }
}

Claude Code can add the endpoint with claude mcp add --transport http squadcard https://squadcard.app/api/mcp. Codex uses codex mcp add squadcard --url https://squadcard.app/api/mcp, followed by codex mcp login squadcard. The repository also includes a Claude Code plugin and Codex configuration.

If the agent runs without a browser, create an AI-agent key in the Squadcard account settings and send it as Authorization: Bearer <key>. The key has the same limits as browser sign-in and can be disconnected from that account page. No environment variables are specified as required.

Tools and capabilities

• make_fair_teams: Split names into two balanced teams and separate the keepers.
• make_fixtures: Produce a round-robin schedule for three to 16 teams.
• suggest_team_names: Generate names from a theme or word.
• list_squads, get_squad: Find the signed-in person's squads and inspect a squad, invite link, next game, and attendance.
• create_squad, join_squad: Create a squad or join one using an invite link.
• set_game, answer_game: Set the match details and record an in, maybe, or out response.
• pick_teams, reshuffle_teams: Make an initial balanced split or another split of the same players.
• enter_result, get_match: Save a score and obtain the voting link, or inspect a match's teams, score, and turnout.

Limitations and notes

The Squadcard MCP server cannot see how participants voted, mark payments, buy items, remove players, or delete anything. Authentication is required before account-related actions can be used. The fixture generator accepts between three and 16 teams; the material does not specify a wider range.

The repository is licensed under MIT. The documented clients include Claude Desktop, Cursor, VS Code, Claude Code, and Codex; the HTTP endpoint can also be configured in other MCP clients that support this transport and authentication pattern.