Tabcorp

Tabcorp MCP Server provides a production-ready MCP server to access Tabcorp betting APIs through 28 specialized tools across racing, sports, and account management. It is designed for high performance, secure authentication, and easy integration with client applications that need real-time data and actions from the Tabcorp ecosystem.

How to use

You connect your MCP client to the server URL to perform authentication and fetch data or perform actions. Start by choosing between a remote hosted MCP endpoint for quick access or running the server locally for full control and testing.

How to install

Prerequisites: you need Python installed if you plan to use the Python client examples, and you may use a supported MCP client in JavaScript/TypeScript or other languages as well.

# Option A: Use the live hosted MCP endpoint (no local install required)

# Option B: Run locally

# 1. Clone the project repository
# (Replace with the actual repository URL if you are configuring a local environment)
# git clone https://github.com/bencousins22/tab-mcp.git

# 2. Install dependencies
uv sync  # or: pip install -r requirements.txt

# 3. Configure environment variables
cp .env.example .env
# Edit .env with your Tabcorp API credentials

# 4. Start the development server
uv run dev  # Server starts on http://localhost:8081

# 5. Run tests (requires credentials for integration tests)
pytest tests/unit -v
pytest tests/integration -v  # Requires API credentials

Configuration and usage notes

Environment variables are used to configure OAuth credentials and API access. Create a .env file in your project root and populate the keys shown below. The server reads these values at startup to authenticate with Tabcorp APIs and to enable per-session customization.

# OAuth Credentials (Required)
TAB_CLIENT_ID=your_client_id
TAB_CLIENT_SECRET=your_client_secret

# Personal Account (Optional - for betting features)
TAB_USERNAME=your_tab_account
TAB_PASSWORD=your_tab_password

# API Configuration
TAB_BASE_URL=https://api.beta.tab.com.au
DEFAULT_JURISDICTION=NSW

Security and best practices

Never commit credentials to version control. Use environment variables and .env files which are gitignored. Rotate credentials on a regular cadence and enable two-factor authentication on accounts with access to the MCP server.

Deployment and running modes

For quick access, you can use the live hosted endpoint. For full control and local testing, run the development server locally and connect your MCP client to http://localhost:8081.

Testing

Run unit and integration tests to validate behavior. Integration tests require API credentials to access the remote services.