IRacing 🐎 MCP Server

Node.js mcp server for iRacing data api

Local serverstdioTypeScript

What is the IRacing 🐎 MCP server?

Most developer tooling work still happens through a UI a human drives. IRacing 🐎 MCP server moves it into the conversation instead. Node.js mcp server for iRacing data api.

The short version

A Node.js Model Context Protocol (MCP) server that provides seamless access to iRacing's racing simulation data API. This project serves as both a standalone CLI tool and an MCP server for AI assistant integration.

The tools it exposes

The server publishes 7 tools. What each one is for:

  • login — Authenticate with iRacing
  • get_members_profile — Get member profile data
  • get_team — Retrieve team information
  • get_member_recap — Get season recap data
  • get_member_career — Get career statistics
  • driver_lookup — Search for drivers
  • Prerequisites — The Prerequisites tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: COOKIE_JAR, EMAIL, API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js 24+ - npm - iRacing account with active subscription

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. IRacing 🐎's toolset — login, get_members_profile, get_team and 4 more — is a fair guide to whether it matches your workflow. It is maintained by emilioSp; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against IRacing 🐎's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
loginAuthenticate with iRacing
get_members_profileGet member profile data
get_teamRetrieve team information
get_member_recapGet season recap data
get_member_careerGet career statistics
driver_lookupSearch for drivers
PrerequisitesThe Prerequisites tool exposed by this server.

How to install the IRacing 🐎 MCP server

{
  "mcpServers": {
    "iracing-data-mcp-server": {
      "command": "npx",
      "args": [
        "iracing-data-mcp-server@latest",
        "@modelcontextprotocol/server-filesystem",
        "/path/to/your/cookie-jar-file"
      ]
      "env": {
        "COOKIE_JAR": "/path/to/your/cookie-jar-file",
        "EMAIL": "your.email@example.com",
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 24+ - npm - iRacing account with active subscription
VariableDescriptionRequired
COOKIE_JARConfiguration value read at startup.Optional
EMAILConfiguration value read at startup.Optional
API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use IRacing 🐎 to login.
  • Use IRacing 🐎 to get members profile.
  • Use IRacing 🐎 to get team.

Frequently asked questions

Use your iRacing email and password, or generate a SHA‑256 API key from your password and email for enhanced security.