Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
ourpr. is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Measured race courses, open to all, and your own runs, Blocks and plans once you sign in.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ourpr-mcp https://ourpr.app/api/mcp
# 2 — ask your agent for something these tools do
# ourpr_list_courses, ourpr_get_course, ourpr_get_course_terrain and 15 more
ourpr. costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
JOAll 3 servers
joeyaflores3 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ourpr-mcp https://ourpr.app/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List every running course published on ourpr., with its place, distance, climb and next race date. Each course is a MEASURED centerline built from recorded runs, with elevation from a public terrain model: USGS 3DEP 10 m in the US, and the city's own 1 m model in Berlin. It is not a course map traced by hand. START HERE. Every other course tool takes a slug, and this is where slugs come from. A
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Match against the course name and its place. Case-insensitive, partial. Example: 'boston', 'fort worth', 'half'. |
| kind | string | no | Keep only this kind. 'race' is a published event course, 'trail' is a trail segment, 'route' is an everyday loop. |
| course_type | string | no | Keep only this shape of course. |
| min_distance_mi | number | no | Keep only courses at least this long, in miles. |
| max_distance_mi | number | no | Keep only courses no longer than this, in miles. |
| upcoming_only | boolean | no | Keep only courses whose next race date is today or later. A course with no date is dropped by this filter. |
| limit | integer | no | The most courses to return. |
| offset | integer | no | How many courses to skip. Use it with next_offset. |
| response_format | string | no | Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation. |
Read one published course: its place, distance, climb, how it was measured, and which streets carry it. DELIBERATELY WITHOUT the elevation profile, the amenities and the centerline. Those are three more tools, because one course payload is about 83 KB and 91% of it is the profile. Args: - slug (string): From ourpr_list_courses. Example: 'boston-marathon'. - response_format ('markdown' | 'jso
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The course's slug, exactly as ourpr_list_courses returns it. Example: 'boston-marathon'. |
| response_format | string | no | Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation. |
The elevation profile of one course, sampled, plus every climb and descent ourpr. named on it. THIS IS THE TOOL FOR "what are the hills and where". Each named section carries the street it runs on, the miles it spans, its net rise or fall and its average grade. The elevation comes from a public terrain model sampled along the measured centerline (elevation_source names it), not from a watch baro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The course's slug. |
| points | integer | no | How many elevation samples to return. The stored profile holds up to 4,873 points, which no agent should read whole. 40 describes the shape; 200 is close to the source. |
| response_format | string | no | Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation. |
Public drinking water and toilets on the line of one course, each placed at the mile it sits at. READ THIS LIMIT BEFORE YOU ANSWER. These come from OpenStreetMap: public taps and toilets somebody mapped near the route. It is a FREQUENCY difference, not a category one — a race day sets up many more stops than an ordinary day has. A mapped tap can also be seasonal, shut off or gone. Never present t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The course's slug. |
| response_format | string | no | Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation. |
Where a course actually runs: its start, its finish, its bounding box, every mile marker, and the streets in the order you meet them. The GPX file is free and needs no account. Hand gpx_url to a person who wants the course on a watch. Args: - slug (string): From ourpr_list_courses. - include_polyline (boolean): Add the encoded centerline, about 9,800 characters. Default false. - response
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The course's slug. |
| include_polyline | boolean | no | Add the encoded centerline. It runs to about 9,800 characters and only helps if you will decode it. Leave it off and hand over gpx_url instead. |
| response_format | string | no | Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation. |
List every trail system ourpr. maps. A trail system is a whole network of connected paths, measured end to end, not a single route through it. Args: - response_format ('markdown' | 'json'): Default 'markdown'. Returns: { "count": number, "trail_systems": [{ "slug": string, // "trinity-trails" "name": string, "region": string | null, // "Fort Worth, TX"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| response_format | string | no | Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation. |
Read one trail system: how many miles of path it holds, how many ways were mapped, where it sits, and where the measurement came from. Args: - slug (string): From ourpr_list_trail_systems. Example: 'trinity-trails'. - response_format ('markdown' | 'json'): Default 'markdown'. Returns: { "slug": string, "name": string, "region": string | null, "total_mi": number, // every
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The trail system's slug. Example: 'trinity-trails'. |
| response_format | string | no | Output format. 'markdown' reads well in a chat answer. 'json' carries every field for further computation. |
Training history between two dates, newest first: date, local start, name, type, miles, pace, time, elevation, average heart rate, and on a runs-only list Friel's efficiency factor and the heartbeats each mile took. Start here for totals, streaks, trends, or finding a run. For one run's splits, use ourpr_get_run with an id from here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | yes | First day to include, YYYY-MM-DD. Example: 2026-01-01 |
| end_date | string | yes | Last day to include, YYYY-MM-DD. Example: 2026-06-30 |
| include_non_runs | boolean | no | Include rides, gym and other types. Runs only by default. |
| limit | integer | no | Most rows to return. The answer says what it left out. |
One activity in full: mile splits with heart rate, cadence, calories, device. Id comes from ourpr_list_runs. For the profile along the route, use ourpr_run_stream.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_id | string | yes | Run id from ourpr_list_runs. |
A run's profile on a 10 m grid — elevation, heart rate, power, cadence — as min, average, max and coverage per channel, not every sample. Also each half by distance with its moving pace, heart rate and efficiency, the pace change between them, and the drift (aerobic decoupling, Pa:HR), also after the warm up. No profile is a normal answer for an indoor run.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_id | string | yes | Run id from ourpr_list_runs. |
The laps the watch recorded for one run — the runner's own button presses. Laps follow the workout; mile splits follow the mile.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_id | string | yes | Run id from ourpr_list_runs. |
Interval sessions found across the history, with reps and distances. Detection is conservative, so a session it misses is still in ourpr_list_runs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many recent activities to read. |
Whether one particular run was an interval session, and its reps.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activity_id | string | yes | Run id from ourpr_list_runs. |
Stretches of past runs matching a distance and climb — what the runner has already done that resembles a race they are training for.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| miles | number | yes | Target distance in miles. |
| gain_ft | number | yes | Target climb in feet. |
| limit | integer | no | How many to return. |
| tolerance_ft | number | no | Climb tolerance, feet. |
The goal race and its Block: race day, distance, goal time, which week of the Block today falls in, and miles for each week. Also the Blocks before past races, each with its result, weeks and peak week. A Block is the race-anchored Monday to Sunday weeks before a race.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| past | integer | no | How many past Blocks to include, newest first. |
Every race ourpr. finds in the history, newest first, tune-ups included: date, name, distance, time, pace and run id. Also the fastest result at 5K, 10K, half marathon and marathon among them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| distance | string | no | Only races at this distance. |
| limit | integer | no | Most rows to return. |
The runner's planned runs between two dates: day, name, miles, time, tag, the runner's note, whether a logged run fulfilled it, and whether ourpr. create wrote it. Read it before ourpr_plan_week so a new plan does not land on a day that already holds one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | First day, YYYY-MM-DD. Default yesterday, so today is in the window in every time zone. |
| end_date | string | no | Last day, YYYY-MM-DD. Default 13 days after the first. |
Write one planned run, or a week of them, onto days still ahead. Each lands on the runner's week as a plan they can see, edit and remove. Needs a token made with the write scope and ourpr. create. Never logs a run.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plans | array | yes | One run, or up to fourteen. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ourpr. or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish ourpr. can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.