mcpField
R
RaceHooks

RaceHooks

Local
racehooks.ioGames & Entertainment1Updated 1d ago

About RaceHooks

RaceHooks is an MCP server for F1 analytics, live timing, and account operations, aimed at AI assistant users. It combines race and telemetry data with tools for managing webhooks, usage, and session replays.

Key features

  1. 01Live session timing and event schedules
  2. 02Race results, strategy analytics, and telemetry
  3. 03Driver, constructor, circuit, and season history
  4. 04Webhook setup, testing, and delivery logs
  5. 05Account plan, billing, and usage metrics
  6. 06Recorded session replay tools

Use cases

  1. 01Check current session status and race timing
  2. 02Compare driver performance and tyre degradation
  3. 03Create and monitor race-data webhooks
  4. 04Review delivery usage and replay recorded sessions

MCP support

Exposes RaceHooks account data through MCP tools, read-only resources, and guided prompts. Requests use the configured account credentials and data availability depends on the account plan.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"racehooks-racehooks": {
"command": "npx",
"args": [
"-y",
"@racehooks/mcp"
],
"env": {
"RACEHOOKS_CLIENT_ID": "<RACEHOOKS_CLIENT_ID>",
"RACEHOOKS_CLIENT_SECRET": "<RACEHOOKS_CLIENT_SECRET>",
"RACEHOOKS_BASE_URL": "<RACEHOOKS_BASE_URL>"
}
}
}
}
Run commandnpx -y @racehooks/mcp
Environment variables to set
RACEHOOKS_CLIENT_IDYour RaceHooks client ID. Get yours at racehooks.io.
RACEHOOKS_CLIENT_SECRETSecretYour RaceHooks client secret.
RACEHOOKS_BASE_URLAPI base URL. Defaults to https://api.racehooks.io.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@racehooks/mcp0.4.1

Tools

59

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
limitintegerNo

Details

From the project README

@racehooks/mcp

MCP server for RaceHooks — gives AI assistants (Claude, Cursor, Windsurf) direct access to RaceHooks motorsport analytics and data.

npm License: MIT

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.

What this does

Exposes your RaceHooks account to an AI assistant as 58 tools, 7 resources, and 6 guided prompts. Every call is made with your account's credentials, so what a tool returns depends on your plan (Free, Developer, or Custom). The data tools cover Formula 1.

Tools

Live

ToolWhat it doesKey argsPlan
get_live_sessionCurrent session state: flag, lap, running order, intervals, tyres, race control messages. Empty when nothing is live.—All (Free gets the latest milestone classification instead of live timing)
list_eventsRace weekends with session schedules and status.year, upcoming, limitAll

Post-race insights

ToolWhat it doesKey argsPlan
list_insight_racesRaces with a completed post-race analytics bundle.seasonAll
get_race_insightsPer-driver, per-lap model outputs (pit, safety car, overtake, undercut, tyre health, cliff risk, LTOE, win probability, expected points) plus pit stops, stints, and lap times.raceIdAll (Free gets tyre state only; strategic predictions need Developer+)
get_model_metaPublic model manifest: what each model predicts, model family, calibration tier, last trained.—All
get_session_analyticsPer-lap analytics snapshot for a session.sessionIdDeveloper+
get_race_summaryPost-race analytics status and aggregate telemetry metrics.raceIdAll (aggregates need Developer+)

Races

ToolWhat it doesKey argsPlan
get_raceRace details with results and qualifying grid.raceIdAll (timing fields need Developer+)
get_race_qualifyingQualifying results.raceIdAll (Q1/Q2/Q3 times need Developer+)
get_race_pitstopsPit stop records (driver, stop, lap, duration).raceIdAll
get_race_tyresTyre stints (compound, lap range, tyre age).raceIdAll
get_race_weatherLap-by-lap weather.raceIdAll
get_race_lapsPer-lap times and positions.raceId, driverIdDeveloper+
get_event_pacePractice and qualifying pace summary per driver.eventIdDeveloper+

History (drivers, constructors, circuits, seasons)

ToolWhat it doesKey argsPlan
list_driversDrivers, searchable.search, nationality, active, limit, offsetAll (page size 25 on Free, 100 paid)
get_driverDriver profile with career stats.driverIdAll
get_driver_resultsRace-by-race results for a driver.driverId, seasonAll (timing fields need Developer+)
get_driver_standingsChampionship standings history for a driver.driverId, seasonAll
list_constructorsConstructors.lineage, active, limit, offsetAll
get_constructorConstructor profile with lineage history.constructorIdAll
get_constructor_resultsRace-by-race results for a constructor.constructorId, seasonAll (timing fields need Developer+)
get_constructor_standingsChampionship standings history for a constructor.constructorId, seasonAll
list_circuitsCircuits with location.country, limit, offsetAll
get_circuitCircuit details and analytics.circuitIdAll
list_seasonsSeasons with race counts.—All
get_season_standingsFinal driver and constructor standings for a season.yearAll
get_season_racesRaces in a season.yearAll

Telemetry

ToolWhat it doesKey argsPlan
get_telemetry_lapsPer-lap telemetry aggregates (speed, throttle, brake, DRS, aggression).raceId, driverId, lapNumberDeveloper+
get_telemetry_driver_lapsPer-lap telemetry for one driver.raceId, driverIdDeveloper+
get_telemetry_lap_comparisonEvery driver's telemetry for one lap.raceId, lapNumberDeveloper+
get_telemetry_race_summaryRace-level telemetry summary.raceIdDeveloper+
get_race_telemetry_lapsPer-lap telemetry metrics from the race data API.raceId, driverIdDeveloper+
get_race_telemetry_stintsPer-stint telemetry and degradation slopes.raceId, driverIdCustom
get_race_telemetry_aggressionDriver aggression index rankings.raceIdCustom

Fantasy

ToolWhat it doesKey argsPlan
get_fantasy_scoresEstimated F1 Fantasy points per driver with full breakdown.raceIdDeveloper+
get_fantasy_pit_timesPit-stop time leaderboard (stationary time) for a session.sessionIdDeveloper+

Account, usage and webhooks

ToolWhat it doesKey argsPlan
list_feedsFeed catalog with the plan each feed requires.limitAll
list_webhooksWebhook subscriptions on the account.limit, offsetAll
get_webhookOne webhook by ID.webhookIdAll
create_webhookCreate a webhook; returns the signing secret once.feedId, webhookUrl, webhookMethod, filtersAll
update_webhookChange URL, method, or filters; pause/resume with active.webhookId, webhookUrl, filters, activeAll
delete_webhookDelete a webhook.webhookIdAll
test_webhookSend a test payload now.webhookIdAll
get_webhook_logsRecent delivery logs.webhookId, limitAll
get_webhook_secretCurrent signing secret.webhookIdAll
rotate_webhook_secretRotate the signing secret (old one stops working immediately).webhookIdAll
get_subscriptionTier, plan limits, and usage snapshot.—All
get_usageDeliveries and failures this period, remaining bucket.—All
get_usage_by_feedDeliveries by feed this period.—All
get_usage_latencyDelivery latency percentiles by feed.—All
get_usage_hourlyHourly deliveries for the last 24 hours.—All
get_usage_historyDelivery history across past periods.—All
get_billing_planCurrent plan, limits, usage this period, and billing period dates.—All

Session replay

ToolWhat it doesKey argsPlan
list_replay_sessionsRecorded sessions that can be replayed.year, type, limit, offsetAll (Free and Developer: current season only)
get_demo_sessionThe curated demo session to replay.—All
get_replay_quotaReplay delivery quota (distinct-session slots) for your tier.—All
prepare_replayPrepare a session's playback artifact.sessionIdAll
get_replay_statusWhether a session's playback artifact is ready.sessionIdAll
Resources (read-only context)
  • racehooks://feeds — full feed catalog
  • racehooks://live — current live session state
  • racehooks://webhooks — all webhook subscriptions
  • racehooks://usage — current delivery usage
  • racehooks://drivers — current-season driver roster
  • racehooks://circuits — circuits with location
  • racehooks://seasons — seasons with race counts
Prompts (guided workflows)
  • setup_race_event_webhook — create an events.race subscription with filters
  • setup_fantasy_scoring_webhook — create a fantasy-optimised subscription
  • check_account_health — full account health summary
  • analyze_race_strategy — pit strategy, tyre management, and model predictions for one race
  • compare_drivers — two drivers head-to-head across a race
  • explain_ml_predictions — what the models predicted vs what happened in the latest analysed race

Installation

npm install -g @racehooks/mcp

Or run directly with npx:

npx @racehooks/mcp

Get your API credentials at racehooks.io.

Configuration

Two environment variables are required; the server exits on start-up without them:

export RACEHOOKS_CLIENT_ID="your-client-id"
export RACEHOOKS_CLIENT_SECRET="your-client-secret"
# Optional — defaults to https://api.racehooks.io
export RACEHOOKS_BASE_URL="https://api.racehooks.io"

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "racehooks": {
      "command": "npx",
      "args": ["-y", "@racehooks/mcp"],
      "env": {
        "RACEHOOKS_CLIENT_ID": "your-client-id",
        "RACEHOOKS_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Claude Code

Claude Code does not read MCP servers from .claude/settings.json. Add the server with the CLI:

claude mcp add racehooks \
  -e RACEHOOKS_CLIENT_ID=your-client-id \
  -e RACEHOOKS_CLIENT_SECRET=your-client-secret \
  -- npx -y @racehooks/mcp

Add --scope project to write it to a shared .mcp.json in your project, or --scope user to make it available in every project. To check the file in without committing secrets, reference environment variables in .mcp.json:

{
  "mcpServers": {
    "racehooks": {
      "command": "npx",
      "args": ["-y", "@racehooks/mcp"],
      "env": {
        "RACEHOOKS_CLIENT_ID": "${RACEHOOKS_CLIENT_ID}",
        "RACEHOOKS_CLIENT_SECRET": "${RACEHOOKS_CLIENT_SECRET}"
      }
    }
  }
}

Cursor / Windsurf

Add to your MCP config (.cursor/mcp.json or equivalent):

{
  "mcpServers": {
    "racehooks": {
      "command": "npx",
      "args": ["-y", "@racehooks/mcp"],
      "env": {
        "RACEHOOKS_CLIENT_ID": "your-client-id",
        "RACEHOOKS_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Cline

In Cline, open MCP Servers → Installed → Configure MCP Servers and add to cline_mcp_settings.json:

{
  "mcpServers": {
    "racehooks": {
      "command": "npx",
      "args": ["-y", "@racehooks/mcp"],
      "env": {
        "RACEHOOKS_CLIENT_ID": "your-client-id",
        "RACEHOOKS_CLIENT_SECRET": "your-client-secret"
      },
      "disabled": false
    }
  }
}

Example usage with Claude

Once configured, you can ask Claude things like:

"Check my RaceHooks account health"

"Create an events.race webhook for https://myapp.com/hook, filtering for Ferrari only"

"Compare VER and NOR tyre degradation in the last race"

"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"

Security

The MCP server runs as a local stdio process — it never binds a network port. Your credentials are passed via environment variables, are sent only to the RaceHooks API (to obtain an access token), and are never included in tool calls or resource URIs.

All API calls are authenticated using OAuth 2 client credentials (token auto-refreshes before expiry).

Links

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.