sportscore-mcp

MCP server for SportScore — live scores, match details, standings, top scorers, brackets and player stats across football, basketball, cricket and tennis. Free public API, CORS-open, no API key.

Works in any Model Context Protocol host: Claude Desktop, Cursor, Continue, Zed, and custom MCP clients.

What it gives your AI assistant

• Live + recent matches by sport

• Single match detail (score, status, timeline, lineups)

• Team schedules

• League / competition standings

• Top scorers / top assisters

• Player statistics and metadata

• Knockout tournament brackets

• Live match tracker data

Install in Claude Desktop

Add this to claude_desktop_config.json:

macOS — ~/Library/Application Support/Claude/claude_desktop_config.json Windows — %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "sportscore": {
      "command": "npx",
      "args": ["-y", "sportscore-mcp"]
    }
  }
}

Restart Claude Desktop. You should see the SportScore tools in the tools menu. Ask things like:

• "What Premier League matches are live right now?"

• "Show me the NBA standings."

• "Who are the top scorers in La Liga?"

• "What's Barcelona's next fixture?"

Install in Cursor / Continue / Zed

Any MCP host that accepts a stdio command works. The npx -y sportscore-mcp invocation is the same — consult your host's MCP docs for the exact config file.

Configuration

Environment variables (optional):

Anonymous install-ping (opt-out)

On startup the server fires one fire-and-forget POST to https://sportscore.com/api/mcp/ping/ with this payload:

{ "client": "sportscore-mcp", "version": "0.3.0", "transport": "stdio", "host": "darwin", "node": "20.11.0" }

That's the whole payload — no user id, no IP, no cookies, no fingerprint. We use it to see rough weekly-active-installs and Node/OS spread so we know what to support. Opt out with SPORTSCORE_NO_TELEMETRY=1.

Tools

Full parameter docs and response shapes: sportscore.com/developers/ · OpenAPI 3.0 spec

Attribution

This MCP server surfaces a Powered by SportScore attribution with every tool result. The free-tier API requires that attribution to remain visible in end-user-facing output — so please don't strip it from your prompts or post-processing.

Commercial / white-label use that needs to remove the attribution: api@sportscore.com. Terms: sportscore.com/developers/terms/.

Rate limits

Free tier: approximately 1000 requests / 24h / IP, with 60-second edge caching. Sensible for any MCP workflow — a user driving a chat session will not approach the limit. Bulk / production / higher-volume use: contact api@sportscore.com.

License

MIT — see LICENSE.

Links

• SportScore

• Developer portal + REST API docs

• OpenAPI 3.0 spec

• API terms of use

• Report an issue