Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read your SisRUN (appsisrun.com.br) training plan: prescribed workouts, pace/HR windows, structure
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SISRUN_EMAIL, SISRUN_PASSWORDValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"sisrun": {
"command": "uvx",
"args": [
"sisrun-mcp"
],
"env": {
"SISRUN_EMAIL": "your-value",
"SISRUN_PASSWORD": "your-value"
}
}
}
}Run this in your terminal
claude mcp add sisrun --env SISRUN_EMAIL=your-value --env SISRUN_PASSWORD=your-value -- uvx sisrun-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sisrun": {
"command": "uvx",
"args": [
"sisrun-mcp"
],
"env": {
"SISRUN_EMAIL": "your-value",
"SISRUN_PASSWORD": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"sisrun": {
"type": "stdio",
"command": "uvx",
"args": [
"sisrun-mcp"
],
"env": {
"SISRUN_EMAIL": "your-value",
"SISRUN_PASSWORD": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
SISRUN_EMAIL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account cdutr, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: SISRUN_PASSWORD
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Aiterm MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
🇧🇷 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.
| Tool | What it returns |
|---|---|
get_current_week() | Every workout row of the current week |
get_week(date) | The week containing an ISO date (YYYY-MM-DD) |
get_upcoming(weeks_ahead=1) | Prescribed-but-not-done workouts from today forward |
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).
`planned_km` vs `distance_km`: 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). planned_km derives the honest number from the coach's structured session, expanding Repetir Nx blocks; planned_km_is_est: "yes" marks rows where a timed step had to be converted at an assumed pace.
uvx sisrun-mcp # zero-install run from PyPI
pipx install sisrun-mcp
uvx --from git+https://github.com/cdutr/sisrun-mcp sisrun-mcp
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.
{
"mcpServers": { "sisrun": { "command": "uvx", "args": ["sisrun-mcp"] } } }
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).
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.
Bug reports, feature suggestions and PRs are welcome, in English or Portuguese. See CONTRIBUTING.md.
mcp).Servidor MCP não oficial que expõe sua planilha de treinos do SisRUN (appsisrun.com.br) para assistentes de IA como o Claude. Com ele você pergunta "o que o treinador prescreveu essa semana?" e recebe os treinos estruturados: status (Proposto / Feito / Feito Avulso), distância, faixas de ritmo e FC, a estrutura da sessão (aquecimento, tiros, recuperações), a observação do treinador e o que o SisRUN associou como realizado (o SisRUN importa suas atividades do Garmin/Strava automaticamente).
O SisRUN não tem API pública, então o servidor lê as mesmas páginas que você vê no navegador, com as suas próprias credenciais. É somente leitura: nunca escreve nada no SisRUN.
Ferramentas: get_current_week() (semana atual), get_week(date) (semana de uma data), get_upcoming(weeks_ahead) (treinos propostos daqui pra frente).
Instalação:
uvx sisrun-mcp
pipx install sisrun-mcp
Credenciais: seu próprio login do SisRUN, por variáveis de ambiente (SISRUN_EMAIL / SISRUN_PASSWORD) ou pelo arquivo ~/.sisrun/credentials:
email=voce@exemplo.com
password=suasenha
chmod 600 ~/.sisrun/credentials
⚠️ A senha fica em texto puro. O SisRUN não oferece token nem OAuth, então não existe opção melhor. Mantenha o arquivo com chmod 600 e nunca faça commit dele.
Sobre `planned_km`: o campo Distância do próprio SisRUN fica vazio em todo treino intervalado, de subida ou por tempo, e em dias de tiro conta só as repetições. Somar essa coluna subestima a prescrição real em ~35% (o painel "Evolução Semanal" do próprio SisRUN tem esse mesmo bug). O planned_km deriva o número honesto a partir da sessão estruturada do treinador, expandindo os blocos Repetir Nx.
Avisos: projeto não afiliado, não endossado e não suportado pelo SisRUN. Pode quebrar quando o site mudar (issues e PRs são bem-vindos). Ele acessa apenas os seus dados, com as suas credenciais, a mesma portabilidade de dados que a LGPD garante a você. Não use contra contas que não são suas e respeite os termos de uso do SisRUN.
Para depurar sem cliente MCP: python -m sisrun_mcp selftest imprime a semana atual em JSON.
MIT