The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the RaceHooks listing page.
MCP server for RaceHooks — gives AI assistants (Claude, Cursor, Windsurf) direct access to RaceHooks motorsport analytics and data.
RaceHooks is an independent service and is not affiliated with or endorsed by Formula One Management or the FIA. "Formula 1," "F1," and related marks are trademarks of Formula One Licensing BV.
Exposes your RaceHooks account as a set of tools and resources an AI assistant can call:
Tools (actions):
list_feeds / list_webhooks / get_webhook / create_webhook / delete_webhooktest_webhook / get_webhook_logsget_live_session / list_eventsget_subscription / get_usage / get_usage_by_feed / get_billing_planstart_simulation / list_simulations / get_simulation / cancel_simulationResources (read-only context):
racehooks://feeds — full feed catalogracehooks://live — current live session stateracehooks://webhooks — all webhook subscriptionsracehooks://usage — current delivery usagePrompts (guided workflows):
setup_race_event_webhook — create an events.race subscription with filterssetup_fantasy_scoring_webhook — create a fantasy-optimised subscriptioncheck_account_health — full account health summaryOr run directly with npx:
Get your API credentials at racehooks.io.
Set two environment variables before starting:
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
Add to .claude/settings.json in your project:
Or with npx (no global install needed):
Add to your MCP config (.cursor/mcp.json or equivalent):
Once configured, you can ask Claude things like:
"Check my RaceHooks account health"
"Create an
events.racewebhook for https://myapp.com/hook, filtering for Ferrari only"
"Start a simulation of the 2025 Monaco GP qualifying against my webhooks at 10× speed"
"Show me which feeds are using the most delivery quota today"
"Set up a fantasy scoring webhook for my VER, NOR, LEC team at https://scoring.myapp.com/hook"
The MCP server runs as a local stdio process — it never binds a network port. Your credentials are passed via environment variables, not included in tool calls or resource URIs.
All API calls are authenticated using OAuth 2 client credentials (token auto-refreshes before expiry).