playmetrics_mcp

playmetrics_mcp

Read-only MCP server for the PlayMetrics youth-sports club management platform, enabling AI agents to query clubs, teams, players, schedules, registrations, and payments.

Category
访问服务器

README

playmetrics_mcp

First MCP server for the PlayMetrics youth-sports club management platform. Read-only access to clubs, teams, players, schedule, registrations, and payments - so Claude, Cursor, or any MCP client can answer questions about your club's day-to-day operations.

MIT licensed. Built on the mcp-vertical-template standards: shared httpx.AsyncClient with pooling + transport retries, typed exception hierarchy, respx tests, structlog logging, py.typed marker, ruff full-rule-set, mypy --strict, JSONL audit log per tool call.

Why this exists

PlayMetrics is the dominant youth-sports club management platform in the US - purpose-built for the messy workflows of running a club, league, or tournament (registrations, rosters, schedules, payments, communications). The platform just acquired SportsEngine (the AYSO / Pop Warner stack), which makes it the de-facto default for thousands of clubs.

But PlayMetrics does not publish a first-party developer API. Club directors spend hours each week pulling rosters, schedules, and registration status by hand - exactly the kind of work an AI agent should be able to do.

This server reverse-engineers the same api.playmetrics.com backend the web app uses, exposes it as MCP tools, and ships the engineering discipline B2B procurement teams expect (audit logs, isError-compliance, retry with backoff, structured errors).

Features

13 tools across 6 resource groups:

Group Tools
Diagnostic health_check, get_current_role
Clubs list_clubs, get_club
Teams list_teams, get_team
Players list_players, get_player
Schedule / events list_events, get_event, get_schedule, list_upcoming_practices
Registrations & payments list_registrations, get_registration, list_payments

All tools:

  • Raise on failure (FastMCP sets isError=true on the wire - agents can't get stuck retrying).
  • Write one JSONL audit record per call (stderr by default, or PLAYMETRICS_AUDIT_LOG=/path/to/audit.jsonl).
  • Map HTTP failures to a typed exception hierarchy (PlaymetricsAuthError, PlaymetricsNotFoundError, PlaymetricsRateLimitError, PlaymetricsAPIError, PlaymetricsConnectionError).
  • Retry transient 5xx / 429 with exponential backoff + full jitter, honoring Retry-After.
  • Use a shared httpx.AsyncClient with connection pooling and 3 transport retries.

Install

git clone https://github.com/sanjibani/playmetrics_mcp
cd playmetrics_mcp
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"

Auth setup (3 minutes)

PlayMetrics auth is session-based against api.playmetrics.com, not API-key-based. You need three things from your web session:

  1. Email + password - your PlayMetrics login.
  2. role_id - a query parameter PlayMetrics uses to scope a user to one of their many possible contexts (a director might be admin of one club and parent of another player in a different club, each with its own role_id).

To find your role_id:

  1. Log in to https://app.playmetrics.com in your browser.
  2. Open DevTools → Network tab.
  3. Reload the page or click around the Schedule tab.
  4. Find any request to api.playmetrics.com (e.g. /schedule or /events).
  5. Copy the role_id query parameter value from the request URL.

Then set:

export PLAYMETRICS_USERNAME='you@example.com'
export PLAYMETRICS_PASSWORD='your-password'
export PLAYMETRICS_ROLE_ID='the-role-id-from-the-url'
playmetrics_mcp

(Or supply PLAYMETRICS_SESSION_TOKEN=... if you've already minted one via the /login endpoint.)

Example agent prompts

  • "List the teams I'm coaching this season."list_teams
  • "What's the schedule for team X next two weeks?"list_events(start=today, end=today+14d, team_id=X)
  • "When's our next practice?"list_upcoming_practices(team_id=X, days=14)
  • "Show me registrations still pending payment."list_registrations(status=pending)
  • "Pull today's deposits for the treasurer."list_payments(status=paid, ...) + filter client-side

Architecture notes

Reverse-engineered API surface

PlayMetrics does not publish an API reference. The endpoints here were observed in the web app's network traffic and follow the convention: plural nouns, role_id scoped, kebab-case for compound paths (e.g. /events/upcoming).

If PlayMetrics renames an endpoint, point the corresponding method in client.py at the new path - the rest of the stack (auth, retry, audit, typed exceptions) is unaffected. PRs welcome.

Login flow

PlaymetricsClient.__init__ does a synchronous POST /login (using the sync httpx client - no event loop yet) if no PLAYMETRICS_SESSION_TOKEN is present, then reuses the resulting bearer token for every async call that follows. The password is held in memory for re-login, but never logged (the audit redactor strips any field named password or PLAYMETRICS_PASSWORD).

isError-compliance

Every tool body is wrapped so that any PlaymetricsError propagates out and FastMCP wraps it as a ToolError on the wire response - setting isError=true so the agent sees a real failure rather than an error-shaped string. The Blackwell Systems audit (54 MCPs / 20 bugs) and MCPTox benchmark both flagged the opposite pattern as the most common MCP bug class; this server does not regress.

Development

pytest                     # run all tests (no live API)
pytest -m "not integration" # default - no live API
ruff check src tests       # lint
ruff format --check src tests
mypy src                   # type check (strict)

Tests use respx to intercept httpx calls - no live API traffic. The login flow is exercised in-process via respx mocks.

Distribution

Distribution state file: ~/.mavis/state/vertical-mcp/dist/playmetrics-mcp.json. Picked up daily by the vertical-mcp-distribute cron for auto-submission to awesome-mcp-servers, mcp.so, GitHub topics, etc.

Sister MCPs in the same portfolio

License

MIT. See LICENSE. Author: Sanjibani Choudhury schoudhury1991@gmail.com.

Disclaimer

This is an independent, community-built integration. It is not affiliated with, endorsed by, or supported by PlayMetrics, Inc. Use at your own risk - the underlying API is reverse-engineered and may change without notice.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选