Skip to main content

MCP Server

Use Sportmicro through a local MCP server when you want your AI tool to call curated live API tools directly instead of only reading docs and generating code.

The published npm package is:

@sportmicro/sportmicro-mcp-server

Quick start​

1. Get your API key​

Create or copy a Sportmicro API key from the Sportmicro Dashboard.

The MCP server expects:

SPORTMICRO_API_KEY=your_api_key

2. Run the server​

No cloning or building is required for normal usage. The server is published on npm and runs directly via npx.

npx -y @sportmicro/sportmicro-mcp-server

3. Register with your AI tool​

Claude Code​

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": "npx",
      "args": ["-y", "@sportmicro/sportmicro-mcp-server"],
      "env": {
        "SPORTMICRO_API_KEY": "your_api_key"
      }
    }
  }
}

Common config locations:

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

Cursor​

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

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

4. Try it​

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
  • Run the integration_brief prompt for football and a live scores dashboard

Optional: Stack Overflow for Agents​

If you use an agentic coding tool while integrating Sportmicro, you can optionally connect that agent to Stack Overflow for Agents for public troubleshooting and reusable implementation guidance.

This is not required to use the Sportmicro MCP server, and it is not a Sportmicro-specific integration. It is an optional agent capability.

Agent-guided setup:

  • Ask your agent to open https://agents.stackoverflow.com/skill.md and follow the setup instructions.

Skill install setup:

npx skills add https://agents.stackoverflow.com/

Use it for things like:

  • Researching MCP integration patterns
  • Checking TypeScript or tool-schema implementation approaches
  • Sharing public, reusable lessons learned from Sportmicro integrations

Do not share:

  • SPORTMICRO_API_KEY
  • private Sportmicro data
  • internal code or unpublished endpoints
  • customer data

What the MCP server exposes​

The server exposes a curated Sportmicro tool surface plus catalog-backed endpoint access:

  • Supported sports list
  • Server overview and docs links
  • Sport-specific docs and OpenAPI URLs
  • Endpoint discovery by sport
  • Generic documented endpoint calls
  • Live matches
  • Match lookup and date windows
  • Standings
  • Teams by league or season
  • Players by team
  • Match-related detail endpoints

This complements the docs and OpenAPI files. It does not replace them.

Prompts​

The current package exposes these MCP prompts:

  • daily_schedule
  • league_overview
  • match_preview
  • team_overview
  • integration_brief

Resources​

The current package exposes these MCP 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}

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