scouting
Mobile-first game-prep dashboard for a youth baseball coaching staff, ingesting scouting reports and team stats via MCP.
9 commits over 2 days
What it is
Storm Scout is a web app built for the Chanhassen Storm 13U AAA baseball coaching staff to prepare for games. It displays upcoming opponents, the team's own roster stats, and detailed scouting reports scraped from GameChanger. Coaches can view self-scout analysis, opponent batting/pitching breakdowns, and matchup context—all optimized for mobile devices on game day. The app accepts data pushes from a Claude "cowork" project over a remote MCP server, letting an AI assistant parse CSV stats and markdown scouting reports into a structured Postgres database.
Why I built it
Built to solve a real, immediate coaching need: consolidating scattered scouting reports and team stats into a single mobile-friendly interface for game-day decision-making. The inclusion of MCP tooling suggests the developer was experimenting with agentic workflows—using Claude to automate data ingestion and potentially provide matchup reasoning—while solving a genuine problem for his son's baseball team (Carrick O'Neill appears in the roster, and the repo owner is Tom O'Neill, listed as head coach).
Tech stack
Next.js 15 (App Router), TypeScript, React, Tailwind CSS v4, Postgres, Drizzle ORM, mcp-handler (remote MCP server over Streamable HTTP), Docker/Docker Compose for deployment to Dokploy.
Timeline & effort
Last active Jun 17, 2026 — 9 commits across 2 active days (spanning 4 days).
Built in a 4-day sprint (June 13–17, 2026) across 2 active coding days with 9 commits. Tight timeline suggests focused, high-intensity work to ship before a real doubleheader on June 13.
Did it turn out useful?
This is a working, deployed tool solving a genuine problem. It has a full database schema with migrations, seed data from real games, working UI pages for roster/opponents/schedule, a remote MCP server with read/write tools, Docker Compose configs for both local dev and production deployment to Dokploy, and detailed scouting reports already in the repo. The context strongly indicates it was used in production for actual game prep—the scouting reports reference specific opponents the team faced, with real stats and tactical analysis.