F1 MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`NODE_ENV`	No	The Node.js environment mode	production

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
get_session_dataC	Get detailed F1 session data including telemetry, timing, and weather
analyze_tire_performanceC	Advanced tire performance analysis with degradation modeling and strategy insights
analyze_lap_timesC	Sophisticated lap time analysis with fuel correction and mini-sector breakdown
predict_weather_impactC	Weather impact analysis and prediction for race strategy
simulate_race_strategyC	Monte Carlo race strategy simulation with probabilistic outcomes
analyze_driver_performanceC	Driver performance extraction separating skill from car performance
get_real_time_telemetryC	Real-time telemetry data processing with advanced signal analysis
analyze_sector_performanceC	25 mini-sector analysis with track curvature correlation
get_current_season_infoC	Get current F1 season information including live data availability
get_race_scheduleB	Get F1 race schedule for any year including 2025
connect_live_timingB	Connect to F1 Official Live Timing API for real-time data
get_live_timing_statusB	Get status of F1 Live Timing API connection
get_api_statusB	Get status of all F1 data APIs (Ergast, OpenF1, Live Timing)

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

Latest Blog Posts

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stagsz/F1-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server