@aggregator-gg/mcp-server

@aggregator-gg/mcp-server

MCP server for operator-side integration work with The Aggregator.

It gives AI coding tools a practical surface for:

• browsing the Aggregator game catalog;
• narrowing directly to provider inventories such as TRUE LABS;
• creating demo and live sessions through api.aggregator.gg;
• reading rollout guidance for callbacks, donor-port reuse, and first-bet go-live gates.

Install

npm install @aggregator-gg/mcp-server

Or run it directly:

npx @aggregator-gg/mcp-server --api-key sk_live_xxx

What operators can do with it

The package is designed for operator-side agents that work inside the operator's own repository or integration workspace. A typical flow is:

1. Read the quickstart and callback resources.
2. Use assess_operator_readiness to check whether welcome-credit testing or live rollout is realistic.
3. Use list_truelabs_games to pick a launch candidate.
4. Use get_game to confirm metadata and restrictions.
5. Use create_session to create a controlled launch.
6. Use get_session and list_transactions while collecting callback evidence.

For operators that already have another aggregator integration, use plan_port_adaptation to map an existing Hub88, St8, SOFTSWISS, APIgrator, SlotMatrix, CasinoEngine, or SoftGamings port into The Aggregator without rebuilding from zero.

Available tools

• list_games
• list_provider_games
• list_truelabs_games
• get_game
• create_session
• create_demo_session
• get_session
• list_transactions
• list_providers
• provider_health
• assess_operator_readiness
• plan_port_adaptation

Available resources

• aggregator://docs/quickstart
• aggregator://docs/callbacks
• aggregator://docs/truelabs-first-bet
• aggregator://docs/donor-port-adaptation
• aggregator://docs/api-reference

Run locally

npm run build --workspace @aggregator-gg/mcp-server
npx @aggregator-gg/mcp-server --api-key sk_live_xxx

Example MCP client config

{
  "mcpServers": {
    "aggregator": {
      "command": "npx",
      "args": [
        "@aggregator-gg/mcp-server",
        "--api-key",
        "sk_live_xxx"
      ]
    }
  }
}

Live rollout note

Creating a session is not enough proof for TRUE LABS live rollout. Treat live enablement as controlled only after:

• one successful launch;
• accepted bet and win callbacks;
• duplicate retry / idempotency evidence;
• a named rollback owner.