College Football Data MCP Server

Created By
lenwooda year ago
An MCP server enabling CFBD API queries within Claude Desktop.
Overview

What is College Football Data MCP Server?

The College Football Data MCP Server is an implementation that provides access to college football statistics sourced from the College Football Data API within Claude Desktop.

How to use College Football Data MCP Server?

To use the server, install it via Smithery or manually, set up your environment, and run the server. You can then connect it with Claude Desktop to query college football data using natural language.

Key features of College Football Data MCP Server?

  • Query comprehensive college football statistics and data.
  • Access game results, team records, and player statistics.
  • Analyze play-by-play data and drive summaries.
  • View rankings and win probability metrics.
  • Compare team performances and generate insights.

Use cases of College Football Data MCP Server?

  1. Analyzing game statistics and trends.
  2. Retrieving historical data for research purposes.
  3. Comparing team performances for betting or analysis.

FAQ from College Football Data MCP Server?

  • What are the prerequisites?

You need Python 3.11 or higher and a College Football Data API key.

  • Is the server free to use?

Yes, the College Football Data API is free, but it has rate limits.

  • How can I troubleshoot API key errors?

Ensure your API key is correctly set in the configuration files and is valid.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lenwood
Star
9
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago