@sportmicro/sportmicro-mcp-server

Official Model Context Protocol server for Sportmicro APIs.

This package exposes a local stdio MCP server so AI tools can call live Sportmicro endpoints directly instead of only reading docs and generating code. It is designed for Claude Code, Claude Desktop, Cursor, and other MCP-compatible clients.

What it exposes

Tools:

• list_supported_sports
• get_server_overview
• get_sport_docs
• list_sport_endpoints
• call_sport_endpoint
• get_countries
• get_leagues
• get_tournaments_by_league
• get_seasons_by_league
• get_live_matches
• get_match
• get_matches_by_date
• get_matches_by_date_league
• get_standings
• get_teams_by_league
• get_teams_by_season
• get_players_by_team
• get_match_related_data

Prompts:

• daily_schedule
• league_overview
• match_preview
• team_overview
• integration_brief

Resources:

• sportmicro://documentation
• sportmicro://llms
• sportmicro://llms-full
• sportmicro://endpoint-summary
• sportmicro://endpoint-index
• sportmicro://endpoint-index-json
• sportmicro://sport/{sport}/endpoints
• sportmicro://openapi/{sport}

Scope

The server is deliberately split into two layers:

• Curated high-traffic tools for common workflows such as live matches, standings, teams, players, leagues, seasons, and match detail views.
• A validated generic endpoint tool, call_sport_endpoint, for the broader Sportmicro API surface. It checks the route against the published endpoint catalog before calling it.

That keeps the MCP surface compact while still letting clients reach the full documented API.

Environment variables

Required:

SPORTMICRO_API_KEY=your_api_key

Optional:

SPORTMICRO_DOCS_BASE_URL=https://docs.sportmicro.com
SPORTMICRO_API_SCHEME=https
SPORTMICRO_API_DOMAIN_SUFFIX=sportmicro.com
SPORTMICRO_HTTP_TIMEOUT_SECONDS=30
SPORTMICRO_DEBUG_URLS=1

Development

npm install
npm run build
npm run dev

Run the compiled server directly:

node dist/index.js

Run the source version during development:

npx tsx src/index.ts

Local MCP setup

Claude Code

Use the local repo before publishing:

claude mcp add sportmicro \
  --env SPORTMICRO_API_KEY="your_api_key" \
  -- node /absolute/path/to/sportmicro-mcp-server/dist/index.js

Once the package is published to npm, the install command becomes:

claude mcp add sportmicro \
  --env SPORTMICRO_API_KEY="your_api_key" \
  -- npx -y @sportmicro/sportmicro-mcp-server

Claude Desktop

Add this to your MCP config:

{
  "mcpServers": {
    "sportmicro": {
      "command": "node",
      "args": ["/absolute/path/to/sportmicro-mcp-server/dist/index.js"],
      "env": {
        "SPORTMICRO_API_KEY": "your_api_key"
      }
    }
  }
}

After npm publish you can swap command and args to:

{
  "mcpServers": {
    "sportmicro": {
      "command": "npx",
      "args": ["-y", "@sportmicro/sportmicro-mcp-server"],
      "env": {
        "SPORTMICRO_API_KEY": "your_api_key"
      }
    }
  }
}

Cursor

Either add a global MCP server in Cursor settings or use .cursor/mcp.json in a project:

{
  "mcpServers": {
    "sportmicro": {
      "command": "node",
      "args": ["/absolute/path/to/sportmicro-mcp-server/dist/index.js"],
      "env": {
        "SPORTMICRO_API_KEY": "your_api_key"
      }
    }
  }
}

After publish, use:

{
  "mcpServers": {
    "sportmicro": {
      "command": "npx",
      "args": ["-y", "@sportmicro/sportmicro-mcp-server"],
      "env": {
        "SPORTMICRO_API_KEY": "your_api_key"
      }
    }
  }
}

Example prompts

• List the supported Sportmicro sports
• Show me live football matches from Sportmicro
• Get basketball standings for league 1748 and season 4176
• List the documented football endpoints that mention matches
• Call the /moneyline endpoint for hockey with query_json {"match_id":"eq.12345","limit":10}
• Run the integration_brief prompt for football and a live scores dashboard

Publish checklist

1. Create the public repo remote and connect it to this local Git repo.
2. Confirm the npm package name @sportmicro/sportmicro-mcp-server is available.
3. Set any final repository metadata in package.json if you want npm to show source links.
4. Run npm run build.
5. Run npm pack --dry-run.
6. Publish with npm publish --access public.
7. Update the public docs so the MCP setup page can switch from availability-only language to real install instructions.