Log inSubmit server
RaceHooks logo

RaceHooks

F1 data, live timing, analytics, telemetry, webhooks, and replay controls for MCP-compatible AI assistants.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install RaceHooks

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "racehooks": {
      "command": "npx",
      "args": [
        "-y",
        "@racehooks/mcp"
      ],
      "env": {
        "RACEHOOKS_CLIENT_ID": "YOUR_VALUE_HERE",
        "RACEHOOKS_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "RACEHOOKS_BASE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 58 tools correctly (6d ago).

Overview

RaceHooks MCP server connects AI assistants to RaceHooks Formula 1 data and motorsport analytics through MCP tools, resources, and guided prompts. It covers live session state, race results, historical standings, telemetry, model outputs, fantasy scoring, webhooks, account usage, and session replay. Reach for it when an assistant needs to answer F1 questions, inspect race strategy, monitor feeds, or query account data using RaceHooks credentials.

Use cases

  • Monitor a live F1 session
  • Analyze race strategy and tyre management
  • Compare driver telemetry and results
  • Create and test race event webhooks
  • Inspect account delivery usage

Key features

  • Live session state and race timing
  • Race insights and model metadata
  • Historical F1 results and standings
  • Per-lap telemetry analysis
  • Webhook and feed management
  • Session replay controls

Tools58

What RaceHooks lets your agent do. Expand a tool for its parameters.

Verified live~5.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 44d

What it can do

From the 58 tools this server returned when we ran it.

Can delete or modify data · 1Handles credentials · 3Makes network requests · 12Read-only tools · 57
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age99 days
Maintainers1

Observed 2026-10-22 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 17d ago via OSV.dev · @racehooks/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads650Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed58Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How RaceHooks works

What RaceHooks does

RaceHooks MCP server exposes a RaceHooks account to an AI assistant over the Model Context Protocol. The service focuses on Formula 1 data, including live session information, race results, qualifying, pit stops, tyre stints, weather, lap data, driver and constructor history, circuits, seasons, and championship standings.

The RaceHooks MCP server also exposes analytics that go beyond standard results. Depending on the account plan, an assistant can inspect per-lap model outputs, session analytics, telemetry aggregates, tyre degradation, driver aggression, fantasy scoring, and race-level summaries. Webhook management, feed discovery, delivery logs, usage information, billing details, and recorded-session replay are also available.

How it works

The MCP process makes authenticated requests using the configured RaceHooks credentials. The repository documents 58 tools, seven read-only resources, and six guided prompts. Resources provide reusable context such as the feed catalog, live state, webhook subscriptions, usage, current drivers, circuits, and seasons.

Tools accept identifiers and filters appropriate to each operation. For example, an assistant can find a race or driver, request a race-specific result, then inspect laps, tyres, weather, pit stops, or telemetry. Guided prompts provide workflows for setting up event or fantasy webhooks, checking account health, analyzing race strategy, comparing drivers, and reviewing model predictions.

The RaceHooks MCP server respects the account associated with each request. Returned data therefore depends on the subscribed RaceHooks plan. Free accounts have reduced access to some live, timing, analytics, telemetry, and replay details, while Developer and Custom plans unlock additional capabilities described by the service.

Setup and configuration

Install the package globally with npm or run it directly through npx:

Terminal
npm install -g @racehooks/mcp
npx @racehooks/mcp

Set the required credentials before starting the process:

server.ts
export RACEHOOKS_CLIENT_ID="your-client-id"
export RACEHOOKS_CLIENT_SECRET="your-client-secret"

RACEHOOKS_BASE_URL is optional and defaults to https://api.racehooks.io. The server exits during startup if either required credential is missing. API credentials are obtained from RaceHooks. The README includes a Claude Desktop configuration using npx; the same installed process can be registered with an MCP client that supports stdio servers.

Tools and capabilities

The RaceHooks MCP server includes tools for:

  • Reading current session status, event schedules, race results, qualifying, weather, tyres, pit stops, laps, and pace.
  • Searching drivers, constructors, circuits, and seasons, then retrieving profiles, results, standings, and race lists.
  • Querying model metadata, post-race insights, session analytics, and telemetry at race, driver, and lap levels.
  • Managing feeds and webhooks, including creation, updates, tests, delivery logs, secrets, rotation, and deletion.
  • Reviewing subscription, billing, delivery, failure, latency, and historical usage information.
  • Listing replayable sessions, preparing playback artifacts, checking status, and viewing replay quota.

Limitations and notes

This listing concerns Formula 1 data and RaceHooks account access rather than a general motorsport database. Some fields and tools require a paid plan: Developer access is required for several timing, analytics, telemetry, fantasy, and session features, while selected telemetry operations require Custom. Free access may return a latest-milestone classification instead of full live timing and may provide only limited race-insight output.

RaceHooks is independent and is not affiliated with or endorsed by Formula One Management or the FIA. Formula 1-related marks belong to Formula One Licensing BV. Webhook signing secrets should be handled as credentials; the documented rotation behavior invalidates the previous secret immediately.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about RaceHooks

RaceHooks is an MCP server that connects AI assistants to the RaceHooks Formula 1 analytics service. Its main tools cover live session state, race results, telemetry, model insights, driver and constructor history, webhooks, account usage, fantasy scoring, and recorded-session replay, subject to the account’s plan.

Install it with npm or run it with npx: `npm install -g @racehooks/mcp` or `npx @racehooks/mcp`. Configure the resulting stdio process in your MCP client, then provide the required RaceHooks credentials.

RaceHooks requires `RACEHOOKS_CLIENT_ID` and `RACEHOOKS_CLIENT_SECRET`. You may also set `RACEHOOKS_BASE_URL`; if omitted, it uses `https://api.racehooks.io`. The process exits at startup when either required credential is missing.

Yes, the README names Cursor as a supported AI assistant. Configure Cursor to launch the MCP package as a stdio server and provide the required RaceHooks credentials.

The free plan provides access to the listed tools with restrictions. Live access may return the latest milestone classification instead of live timing, race insights may provide tyre state only, and several timing, analytics, telemetry, fantasy, and replay details require higher plans.

Related MCP servers

All in Sports All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRaceHooks AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/racehooks?style=directory)](https://allmcps.com/mcp/racehooks)
HTML Embed
<a href="https://allmcps.com/mcp/racehooks"><img src="https://allmcps.com/api/badge/racehooks?style=directory" alt="RaceHooks on AllMCPs" /></a>