Skip to main content
Glama
parthakker

NFL Analytics MCP

by parthakker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to NFL Analytics MCP

No user-submitted related servers found.

    Related Servers

    • mcp-sports-server

      mayank-nayak
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural-language querying of historical NBA game data from a read-only SQLite database.
      -

    • nfl-mcp

      ebhattad
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides access to over 12 years of NFL play-by-play data through a local DuckDB database. It enables users to query player performance, team statistics, and situational efficiency metrics like EPA and WPA using natural language.
      33 PyPI
      8
      MIT

    • Crocodile

      nazmiefearmutcu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying and replaying deterministic market data for crypto and US equities from a local Parquet lake via natural language.
      2
      Apache 2.0

    • text2sql-agent

      PriyankaHichkad
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants and MCP clients to ask natural-language questions about DuckDB or CSV data and receive safe, read-only SQL-generated tabular insights with automatic schema discovery and multi-table joins.
      -

    • Text2SQL MCP Server

      rajacsp
      A
      license
      Not graded
      quality
      D
      maintenance
      Converts natural language questions into SQL queries and executes them against SQLite databases, returning results as tables or strings.
      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

    A3.5/5.0

    Scored across 19 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: player vs team vs game vs market vs warehouse. Even the news trio is separated by scope, and the kalshi quartet clearly separates listing, detail, snapshot, and history.

    Naming Consistency3/5

    Tool names mix conventions: some are verb-first (predict_game, refresh_data, query_warehouse, describe_warehouse), others are noun-first (team_form, player_lookup, kalshi_markets). The kalshi_ prefix provides local consistency, but the overall pattern is not uniform.

    Tool Count4/5

    With 19 tools, the server is slightly above the ideal 3-15 range, but the comprehensive scope—data ingestion, analytics, news, betting markets, and model reporting—justifies the count. Each tool earns its place.

    Completeness5/5

    The tool surface covers the full lifecycle: data refresh and status, warehouse querying and schema discovery, player/team/coach/referee analytics, news search, betting market analysis, and model prediction/reporting. No obvious dead ends or missing key operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources