EndzoneAPI MCP MCP server

An official MCP server provided by EndzoneAPI that allows AI agents to access comprehensive NFL data, including play-by-play statistics, player injuries, depth charts, and betting odds. It enables users to query historical and current game data, analyze team and player performance metrics, and retrieve schedule information directly through natural language interactions.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by EndzoneAPI

MCP endpoint (Streamable HTTP)

https://mcp.endzoneapi.com/mcp

Vendor documentation

What you can do with it

Retrieve NFL play-by-play data with EPA and win probability
Check player injury status and depth chart positions
Access betting odds and line movement history
Get team and player statistical summaries

Tools advertised by the last live check:

list_teams
get_standings
get_team_stats
get_games
get_schedule
get_game_detail
get_head_to_head
search_players
get_player_stats
get_player_leaders
get_injuries
get_depth_chart
get_snap_counts
get_plays
get_advanced_stats
get_odds
get_line_movement

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http endzoneapi-mcp https://mcp.endzoneapi.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add endzoneapi-mcp --url https://mcp.endzoneapi.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable endzoneapi-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "endzoneapi-mcp": {
      "url": "https://mcp.endzoneapi.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "endzoneapi-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.endzoneapi.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start endzoneapi-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "endzoneapi-mcp": {
      "type": "http",
      "url": "https://mcp.endzoneapi.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http endzoneapi-mcp https://mcp.endzoneapi.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "endzoneapi-mcp": {
      "url": "https://mcp.endzoneapi.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "endzoneapi-mcp": {
      "serverUrl": "https://mcp.endzoneapi.com/mcp"
    }
  }
}

See all 1,583

Do you run EndzoneAPI MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing