Connect over MCP

Ask Claude for live scores, league standings, per-player and per-team stats, Elo ratings, and a machine-readable map of what we hold — answered from real rows, in the conversation you are already having. Connecting takes one URL and a sign-in. There is no API key to paste and nothing to configure.

The server URL

This is the only value you need:

texttext
https://mcp.bigballsdata.com/mcp

Claude

Claude connects from Anthropic's cloud, so the server has to be reachable on the public internet — which this one is. Add it once and it is available in any conversation.

Free, Pro and Max

  1. Open Customize → Connectors.
  2. Click Add custom connector.
  3. Paste the URL above and click Add.
  4. Click Connect and sign in with your BigBalls account.

Team and Enterprise

An organization Owner adds it once, then each member connects their own account:

  1. Owner: Organization settings → Connectors → Add → Custom. If Claude asks for a connector type, choose Web. Paste the URL and click Add.
  2. Members: Customize → Connectors, find the entry labelled Custom, and click Connect.

Each member signs in separately and gets their own account's data and plan limits. One person connecting does not share their key or their quota with the rest of the organization.

In a conversation, use the + button → Connectors to switch it on or off per chat.

Some tools gate connectors behind their own paid plans. That is their policy, not ours, and it changes — so this page does not list which. If your tool offers no way to add a custom or remote MCP connector, use the API key path above or the SDK; nothing here is exclusive to any one assistant.
This works today on Claude Pro and Max — Settings → Connectors, exactly as above. You do not need a Team or Enterprise plan to use it. That requirement applies only to listing a connector in Claude's directory, which is a discovery convenience for everyone else, not a condition of connecting. The two get conflated often enough to be worth stating outright.

Other tools

Any tool that supports remote MCP connectors with OAuth can use the same URL — ChatGPT, Cursor, Perplexity, VS Code with Copilot, Windsurf, Zed, Codex, Grok, Raycast and Warp among them. What differs is only where the “add a connector” setting lives.

We deliberately do not reproduce each vendor's click-path here. They move: ChatGPT's developer-mode toggle alone has lived under Connectors → Advanced, Settings → Apps → Advanced, and Settings → Security and login within the past year, and “Connectors” has since been renamed. A path we copy here is a path that is wrong within months, on a page we cannot re-verify. Each link below goes to the vendor's own documentation, which is the only version that stays current.

ChatGPT

Custom MCP connectors sit behind a developer mode toggle that is switched off by default, which is why people hunt for it. As of 2026-08-25 it is under Settings → Apps & Connectors → Advanced; if it is not there, it has moved — see OpenAI's own article. Turn it on, then add the URL above as a custom connector. On Business and Enterprise workspaces an admin may have to permit custom connectors first.

Editors and terminals

Cursor, VS Code with Copilot, Windsurf, Zed, Codex, Warp and Raycast all take a remote MCP server by URL. Most read the same JSON shape as the config below; the rest have an “add connector” dialog that wants only the URL. Where a tool asks whether the server is local or remote, it is remote.

Anything else

The server speaks JSON-RPC over Streamable HTTP. Clients that support OAuth need nothing but the URL — they discover the authorization server from our 401 and register themselves:

MCP client configjson
{
  "mcpServers": {
    "bigballs-sports-data": {
      "url": "https://mcp.bigballsdata.com/mcp"
    }
  }
}

Clients that do not speak OAuth can send an API key from /dashboard/keys as a bearer token instead:

MCP client config — API keyjson
{
  "mcpServers": {
    "bigballs-sports-data": {
      "url": "https://mcp.bigballsdata.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

What your agent gets

5 read-only tools. Every one of them is annotated read-only — nothing here writes, deletes, or spends anything.

  • get_matches

    Live, upcoming or historical matches for a sport or league.

  • get_standings

    League table with wins, losses, win_pct, games_played.

  • get_player_stats

    Per-player career or per-season totals and per-game rates.

  • get_team_elo

    Team Elo rating, rank and optional rating history.

  • get_coverage

    Machine-readable map of what we hold and what we do not.

Call tools/list against the server for the authoritative signatures — argument names, types and defaults live there rather than being restated here, so they cannot go stale.

Plans and limits

MCP is not a separate product and has no separate pricing. The server is a thin passthrough over the same REST gateway, so your plan, rate limits and entitlements apply exactly as they do to a direct API call. A free account can connect and start asking questions immediately.

If a tool call comes back saying your account has no active API key, sign in to the dashboard once — a key is created on first login, and MCP resolves through it.

Two MCP surfaces, one live server

We also publish a static tool catalogue at /mcp that describes REST endpoints, not this server. It is for tool routers that consume static metadata, and its list is not this server's tool set — the two share exactly one name. The MCP surfaces page explains the difference in full.