iRacing MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IRACING_PASSWORD | Yes | Your iRacing account password. | |
| IRACING_USERNAME | Yes | Your iRacing account username. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_iracing_profile_statsA | Get the current iRacing profile statistics. Retrieves the user's iRacing profile information including license level, iRating, and other career stats. |
| get_irating_chartA | Get the iRating data for a specific license category. Retrieves the user's iRating history data for the specified racing category. This includes historical iRating values that can be used for charting. 1 is oval, 2 is road, 3 is dirt oval, 4 is dirt road, 5 is sports car, and 6 is formula car. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves general profile statistics, the other provides historical iRating data for a specific category. There is no ambiguity between them.
Both tools follow a consistent verb_noun pattern using snake_case and the 'get_iracing_' prefix, making them predictable and easy to understand.
With only 2 tools, the server is severely under-scoped for the iRacing domain, which typically requires many more tools for operations like searching races, managing subscriptions, or accessing car/track data.
The tool surface is extremely limited, covering only profile stats and iRating history. Critical operations like race listing, car/track data, league management, and session results are entirely missing, making it incomplete for practical use.