Skip to main content
Glama
mpizza

baseball-mcp

by mpizza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to baseball-mcp

No user-submitted related servers found.

    Related Servers

    • NHL MCP Server

      dylangroos
      F
      license
      B
      quality
      D
      maintenance
      Provides structured access to NHL data including teams, players, standings, schedules, and statistics through the Model-Context Protocol pattern.
      25
      6
      -

    • MCP Football Server

      yalmeidarj
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time access to football (soccer) data including fixtures, standings, teams, players, transfers, and injuries through the API-Football service via the Model Context Protocol.
      3
      -

    • mcp-mlb-stats

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides access to official MLB statistics via a keyless API, enabling AI agents to query MLB data through natural language or direct tools.
      4 npm
      MIT

    • Formula One MCP Server

      rakeshgangwar
      A
      license
      B
      quality
      D
      maintenance
      Provides Formula One data and statistics through a Model Context Protocol interface, allowing users to access race calendars, session results, driver statistics, telemetry data, and championship standings.
      8
      11
      MIT

    • MLB SportRadar MCP Server

      robcerda
      A
      license
      A
      quality
      D
      maintenance
      Connects Claude to the SportRadar MLB API to access real-time baseball data including game schedules, live scores, player statistics, team standings, injury reports, and play-by-play information through natural language queries.
      19
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct primary purposes: get_daily_results focuses on game outcomes for all teams on a date, get_mlb_schedule provides scheduling information across a date range, and mlb_team_result delivers detailed scoring/highlights for a specific team's recent game. However, there is some overlap between get_daily_results and mlb_team_result in that both can return game results for a date, which could cause minor confusion for an agent.

    Naming Consistency3/5

    The naming is mixed: get_daily_results and get_mlb_schedule follow a consistent verb_noun pattern, but mlb_team_result deviates by placing the domain prefix first and using a noun_verb structure. This inconsistency reduces predictability, though the names remain readable and descriptive.

    Tool Count3/5

    With only 3 tools, the server feels thin for covering the MLB domain comprehensively. While the tools address key aspects like results, schedules, and team details, the limited count may hinder complex agent workflows, such as accessing player stats, standings, or historical data, making it borderline appropriate.

    Completeness2/5

    The tool set has significant gaps for a baseball server. It lacks essential operations like retrieving team standings, player statistics, game box scores, or live scores, and there is no CRUD coverage for user interactions (e.g., favorites or predictions). This incompleteness will likely cause agent failures when handling common baseball queries beyond basic scheduling and results.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources