Tournament Email Draft via claude.ai

story-westside-mcp-tournament-email-draft User Story

active user-story

Project

story: Tournament Email Draft via claude.ai

Role

Admin (Lucas)

Key

tournament-email-draft

Want

As an admin, I want to describe a tournament conversationally inside claude.ai and have a draft email land in Marcus's inbox for approval

So That

So that I can capture tournament email work without leaving claude.ai or routing through Claude Code's multi-step pipeline — drafting becomes a 30-second chat instead of a 16-step orchestration.

Acceptance Criteria

claude.ai connector for westside-mcp surfaces the draft_tournament_email tool with a typed parameter schema (tournament_name, tournament_dates, player_fee, teams)
Calling the tool with all required params produces a plain-text draft rendered from the canonical template
The draft is emailed FROM westsidebasktball@gmail.com TO Marcus (mldraney3@gmail.com) with a [Draft] subject prefix
Marcus reads the draft on his phone and approves out-of-band — no automated player-pool send happens from this MCP tool
Lucas can complete the entire flow (tool call → Marcus has draft) in under 30 seconds from claude.ai, no Claude Code, no terminal, no admin UI

Success Metric

Lucas drafts a tournament email through claude.ai in 30 seconds without opening Claude Code, a terminal, or any westside admin UI. Marcus receives the draft within 60 seconds of Lucas hitting send in claude.ai.

arch:mcp-tools — MCP server tools layer (canonical, see convention-architecture-ids)
arch:postgres — token store (read-only access to basketball-api's oauth_tokens table)

page-westside-mcp — parent project page (to be created as a follow-up)
board-westside-mcp — project board where tickets serving this story live
westside-email-agent — sibling project (the actual email composition and blast logic; this MCP tool drafts something that flows into that pipeline)
notion-mcp-remote, gdocs-daily-mcp-remote — pattern precedents for remote MCP servers