Skip to main content
Glama
Josh-Mantel

F1 MCP Server

by Josh-Mantel

Related Servers

Alternatives to F1 MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides easy access to Formula 1 data including championship standings, event info, season calendars, track visualizations, session results, and driver/constructor info via FastF1 and OpenF1 API.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Formula 1 data analysis through natural language, providing tools like track dominance, lap time analysis, and team performance comparisons.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables access to Formula 1 data from the openF1.org API, including driver information, race results, lap times, telemetry, pit stops, weather conditions, and live position data across multiple seasons.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Formula 1 data through LLM interfaces like Claude. Provides access to F1 information including circuits, constructors, drivers, grand prix, manufacturers, races, and seasons.
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Provides access to Formula 1 data including driver and constructor championship standings with support for current and historical seasons. Enables users to query F1 championship information through natural language with plans for expanded race data and telemetry.
      22
      11 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query real-time and historical Formula 1 data through the OpenF1 API, providing tools for driver info, lap times, telemetry, race events, and more.
      MIT

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting different F1 data aspects: constructor standings, driver standings, lap times, race schedule, and session results. No overlap exists, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive nouns (e.g., get_constructor_standings, get_driver_standings). This uniformity enhances predictability and readability.

    Tool Count4/5

    Five tools are reasonable for an F1 data server, covering key standings and session data. It's slightly lean but well-scoped; minor gaps like historical data or driver details might exist but don't hinder core functionality.

    Completeness4/5

    The tool set covers essential F1 queries: standings, schedules, lap times, and session results. Minor gaps include lack of update/delete operations (typical for read-only data) and potential missing features like pit stop times or weather data, but core workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues