Ourpr MCP server

ourpr-mcp-server

An MCP server that lets an AI agent read your own running history from ourpr, and write one thing back. Ask about your training in plain language, in whatever agent you already use.

Every tool reads. One tool writes, and only that one: ourprplanweek puts a plan on a day still ahead. It cannot log a run, edit history, or issue another credential, and it needs a token made with the write scope.

Why it exists

Every authenticated read in ourpr is gated by a session that lives about an hour, so nothing outside a browser could hold one. Personal access tokens changed that, and this is what they were for: your data, in your tools, with a credential you issued to yourself and can revoke.

Setup

1. Make a token. In ourpr, go to Profile → Settings → ourpr. mcp → New token. Name it after the machine it will live on, and choose Write if you want the agent to plan your week; Read otherwise. Copy it — it is shown once and cannot be recovered. A token lasts 90 days.

2. Point a client at it. The package runs from npm; nothing to clone.

Claude Code

claude mcp add ourpr --env OURPR_TOKEN=ourpr_pat_... -- npx -y ourpr-mcp-server

Claude Desktop

Download ourpr.mcpb from the latest release and open it. Claude Desktop asks for the token and stores it as a secret.

Or edit claudedesktopconfig.json:

{
  "mcpServers": {
    "ourpr": {
      "command": "npx",
      "args": ["-y", "ourpr-mcp-server"],
      "env": { "OURPR_TOKEN": "ourpr_pat_..." }
    }
  }
}

Cursor, VS Code

.cursor/mcp.json or .vscode/mcp.json, same shape as above.

From source

git clone https://github.com/joeyaflores/ourpr-mcp-server.git
cd ourpr-mcp-server
npm install && npm run build && npm test

Environment

The token is an environment variable and not a tool parameter, on purpose: it never changes between calls, so passing it per call would put a live credential into the agent's context, its transcript, and any log of either.

Tools

ourprlistruns

Your history between two dates, as a compact table: date, name, type, miles, pace, moving time, elevation, average heart rate.

Start here for almost anything — totals, streaks, trends, finding a run.

"How many miles did I run in July?"
"What was my longest run this spring?"
"Show me every run over 15 miles in 2026"

startdate, enddate (YYYY-MM-DD), includenonruns, limit.

It never truncates silently: if the window holds more than limit, the answer says how many were left out.

ourprgetrun

One activity in full, with its mile splits, heart rate, cadence, calories and recording device.

"Break down my Boston Marathon splits"
"Did I positive or negative split that half?"

ourprrunstream

A run resampled onto a fixed 10 metre grid — elevation, elapsed time, and where the watch recorded them, heart rate, power and cadence. Returns summary statistics per channel rather than every sample.

A 404 is a normal answer: indoor runs have no profile.

ourprrunlaps

The laps the watch itself recorded — the runner's own button presses, which is what a track session is actually divided by. Different from mile splits: laps follow the workout, splits follow the mile.

ourprrepworkouts

Every interval session ourpr can find in your history, with the reps and their distance. An empty answer says how many activities were read, because "none found" and "none exist" are different claims.

ourprdetectreps

Ask whether one particular run was an interval session.

ourprsimilarterrain

Runs matching a given distance and climb — how you find what you have already done that resembles a race you are training for.

Shortened. The full README is on GitHub.