Flaim Fantasy

License: MIT MCP Tools Chrome Web Store

Connect your ESPN, Yahoo, and Sleeper leagues, then use Flaim Fantasy in ChatGPT for read-only analysis grounded in your real league. The same MCP service also supports optional manual MCP clients like Claude, Perplexity, and Gemini CLI where their MCP capabilities allow.

Analysis tools are read-only by design. No trades, no drops, no roster changes — just advice. League refresh can update Flaim's connected-league records so newly available seasons show up.

How It Works

The Flaim skill teaches your AI assistant how to behave like a fantasy analyst — which data to pull, how to interpret it, and how to turn it into useful advice. The MCP tools feed it your actual league data. Together, they give a general-purpose AI enough structure to answer like it knows your specific league.

Get Started

1. Sign up at flaim.app
2. Connect your platforms — ESPN via Chrome extension, Yahoo via OAuth, Sleeper by username
3. Leagues discovered — Flaim finds supported leagues where possible; some private leagues or historical seasons may need manual follow-up
4. Pick a default league for AI conversations
5. Use Flaim in AI — open Flaim Fantasy in ChatGPT, or add the MCP URL in an optional manual MCP client such as Claude, Perplexity, or Gemini CLI
6. Optional: install the skill — recommended for agent-skill tools; copy .agents/skills/flaim-fantasy/ into your project or home directory (see The Skill below)
7. Ask questions — "Who should I start this week?", "What's on the waiver wire?", etc.

The Skill

The Flaim skill teaches your AI assistant how to behave like a fantasy analyst — when to use which tools, how to interpret league data, and how to turn that context into useful advice.

Install for Claude Code (or any Agent Skills-compatible tool):

Place the skill in your project's .agents/skills/ directory (cross-platform convention) or in ~/.agents/skills/ for global use:

# Clone or copy the skill directory
cp -r flaim/.agents/skills/flaim-fantasy ~/.agents/skills/flaim-fantasy

The AI will detect and activate the skill automatically when you ask fantasy questions.

MCP Tools

Tool	What it does
get_user_session	Your leagues across all platforms
refresh_leagues	Re-discover connected leagues and update Flaim's league records
get_ancient_history	Past seasons and historical leagues outside the current season
get_league_info	Baseline league context: settings, scoring, roster config, teams/owners
get_roster	Team roster with player stats
get_matchups	Weekly matchups and scores
get_standings	League standings and rankings
get_free_agents	Available players; ESPN/Yahoo include ownership percentages, Sleeper returns identities only
get_players	Player lookup; ESPN and Yahoo can add league ownership, Sleeper ownership is unavailable
get_transactions	Recent adds, drops, waivers, and trades

All tools connect through a single MCP endpoint: https://api.flaim.app/mcp

Supported Platforms

Platform	Sports	Auth
ESPN	Football, Baseball, Basketball, Hockey	Chrome extension or manual cookies
Yahoo	Football, Baseball, Basketball, Hockey	OAuth 2.0
Sleeper	Football, Basketball	Username (public API)

Architecture

Chrome Extension → flaim.app → Auth Worker → Supabase
                      ↓
ChatGPT Apps / manual MCP clients → Fantasy MCP Gateway → ESPN/Yahoo/Sleeper Clients → Platform APIs

• Web App (Next.js on Vercel) — landing/site pages, public live demo, OAuth, league management
• MCP Gateway (Cloudflare Workers) — unified endpoint for all platforms and sports
• Platform Clients (Cloudflare Workers) — ESPN, Yahoo, Sleeper API normalization
• Auth Worker (Cloudflare) — token validation, rate limiting, credential storage
• Supabase — user data, OAuth tokens, credentials

About

Solo indie project — built with care, maintained for the long term. No VC funding, no growth pressure, just a useful tool for fantasy sports fans who use AI.

Development

git clone https://github.com/jdguggs10/flaim.git
cd flaim
corepack pnpm install
cp web/.env.example web/.env.local  # add keys
corepack pnpm run dev

Root, web, and workers use pnpm via Corepack. The Chrome extension is intentionally npm-isolated under extension/ with its own lockfile and release flow.

Document	Description
Architecture	System design, deployment, troubleshooting
Changelog	Release history
Web App	Next.js routes, components, environment
Workers	Cloudflare Workers, MCP tools, ESPN API
Extension	Chrome extension build, Sync Host, CWS

Getting Help

Best-effort support — I'll respond when I can.

• GitHub Issues
• GitHub Discussions

License

MIT License — see LICENSE.