SisRUN Training Plan MCP server

sisrun-mcp

<!-- mcp-name: io.github.cdutr/sisrun-mcp -->

🇧🇷 Versão em português abaixo

Unofficial MCP server that exposes your SisRUN (appsisrun.com.br) training plan to AI assistants like Claude, so you can ask "what did my coach prescribe this week?" and get a structured answer.

SisRUN has no public API, so this reads the same web pages you see in your browser, with your own credentials, and parses them into structured workout data. It is read-only: it never writes anything to SisRUN.

Tools

Each workout row carries: date, status (Proposto = prescribed, Feito = done, Feito Avulso = auto-imported, not prescribed), modality, prescribed distance, pace and HR windows, the coach's structured session (warm-up, repeats, recoveries), the coach's note, and what SisRUN matched as delivered (date, distance, time, avg HR, kcal; SisRUN auto-imports your Garmin/Strava activities).

plannedkm vs distancekm: SisRUN's own Distância field is empty for every interval, hill and time-based session, and on interval days it counts the reps only. Summing that column undercounts the real prescription by ~35% (SisRUN's own "Evolução Semanal" panel has the same bug). plannedkm derives the honest number from the coach's structured session, expanding Repetir Nx blocks; plannedkmisest: "yes" marks rows where a timed step had to be converted at an assumed pace.

Install

uvx sisrun-mcp            # zero-install run from PyPI
# or
pipx install sisrun-mcp
# or straight from GitHub
uvx --from git+https://github.com/cdutr/sisrun-mcp sisrun-mcp

Credentials

Your own SisRUN login (the one your coach gave you). Either environment variables:

export SISRUN_EMAIL=you@example.com
export SISRUN_PASSWORD=yourpassword

or a credentials file:

mkdir -p ~/.sisrun
cat > ~/.sisrun/credentials <<'EOF'
email=you@example.com
password=yourpassword
EOF
chmod 600 ~/.sisrun/credentials

⚠️ The password is stored in plain text. SisRUN offers no token or OAuth mechanism, so there is no better option. Keep the file chmod 600, and never commit it.

Claude Desktop / Claude Code config

{
  "mcpServers": {
    "sisrun": {
      "command": "uvx",
      "args": ["sisrun-mcp"]
    }
  }
}

Debugging

Fetch and print your current week without any MCP client:

python -m sisrun_mcp selftest

If a result ever contains a warning about missing detail panels, the JSF form-state accumulation regressed. Please open an issue with the output (it contains no credentials).

How it works (for the curious)

SisRUN is JSF + PrimeFaces 8.0. Every request carries a javax.faces.ViewState token, and all widget ids are server-generated: they change on any redeploy, so nothing here hardcodes them. Buttons are located by their stable, human-authored title attributes, and the ViewState is re-read from every response. The non-obvious part is that the day detail panels are accordions the server only renders when the request carries their expanded state, accumulated across navigation hops, together with javax.faces.partial.execute=@all. Without that you silently get summary rows with no prescriptions. See the comments in client.py.

The client is deliberately polite: one week per request, spaced 0.6 s apart, and week HTML is cached per process.

Contributing

Bug reports, feature suggestions and PRs are welcome, in English or Portuguese. See CONTRIBUTING.md.

Status & disclaimers

Shortened. The full README is on GitHub.