Pitwall 1.1.1 — fixes a broken install

If you installed Pitwall recently and it didn't work, this is why — and this release fixes it.

The break

Every new install of 1.1.0 failed on startup:

ModuleNotFoundError: No module named 'mcp.server.fastmcp'

MCP Python SDK 2.0 removed mcp.server.fastmcp, which all 79 tools are built on. Pitwall declared only mcp>=1.0.0, so a fresh install resolved to 2.0 and died on import. Existing installs kept working, which is exactly why it went unnoticed.

The fix

mcp is now pinned >=1.0.0,<2. Verified from a clean virtualenv on the built wheel: the SDK resolves to 1.29.0, the server starts, and all tools list correctly.

Also fixed: the startup banner was printing to stdout, which in stdio mode is the JSON-RPC channel itself. It now goes to stderr.

Easier install

uvx is now the documented path — no pip, no virtualenv, no "which python3":

claude mcp add pitwall -- uvx --from "f1pitwall[full]" f1pitwall

First launch downloads the FastF1 stack (~540 MB, about 25 seconds). Every launch after is under a second.

New: install as a Claude Code plugin

The f1 skill now ships alongside the server, so Claude knows which of the 79 tools to reach for and how to explain F1 to someone who's never watched a race:

/plugin marketplace add darshjoshi/pitwall
/plugin install pitwall@pitwall

The skill was also stale — it claimed 67 tools and was missing all 12 live-timing tools. Both corrected against the actual tool definitions.

Upgrading

pip install --upgrade "f1pitwall[full]"

Using uvx? It caches by version, so you'll pick up 1.1.1 automatically on next launch.