Goal Race

Encontre corridas de obstáculos, no estilo HYROX e de trilha, salve-as na sua lista, coloque um plano de treino no seu calendário e registre cada sessão digitando ou por voz.

Servidor MCP hospedado

npx add-mcp 'https://mcp.goalrace.com/mcp'

Instala no Claude Code, Codex, Cursor e outros

Documentação

Goal Race MCP documentation

Goal Race has a remote MCP server so an AI assistant such as Claude or ChatGPT can find races, keep your race list and plan your training on your behalf. For a walkthrough with screenshots, see Connect to Claude or ChatGPT .

Overview

  • Endpoint: https://mcp.goalrace.com/mcp
  • Transport: Streamable HTTP, JSON-RPC 2.0 over POST.
  • State: stateless. Every request carries its own credentials; the server keeps no session between calls.

Authentication

The server uses OAuth 2.1 with PKCE. The authorization server is Supabase Auth, and clients register themselves with dynamic client registration, so there is no client ID or secret to paste.

  • Scope: email.
  • Tokens: access tokens last 1 hour and are renewed with a refresh token by the client.
  • Discovery: protected-resource metadata is served at https://www.goalrace.com/.well-known/oauth-protected-resource/mcp.
  • Revoking access: in Goal Raceunder Settings → AI Integration, or in the assistant's connector list.

On first connect you are sent to a Goal Race page where you sign in and approve what the assistant may do.

Tools

Write tools only change your own data. Read tools never modify anything.

ToolAccessWhat it does
get_calendarReadYour local date and time, your home city, the sessions in a window of days, and the races ahead with days to go. One call for everything an assistant needs before it can answer.
get_training_logReadWhat you planned and what you actually did over a range: sessions, minutes, distance and climb, split by type, and your effort load. Filter by tag. Defaults to this week.
get_sessionReadOne session in full, with the plan, the notes and what was really done.
add_sessionsWriteAdd one session or a whole week in one call. A dry run shows the week before anything is written.
update_sessionWriteChange a session, the day it is on included: title, type, date, time, duration, distance, climb, notes, tags.
log_sessionWriteMark a session done (or undo it), with the actuals, how it felt, how hard it was (RPE 1-10), tags and a note.
remove_sessionsWriteDelete one session, several, or every planned session in a date range. More than one is shown first and deleted only after you say so; completed sessions stay unless you ask.
search_racesReadFind upcoming obstacle, gym and trail races by text, race kind, country, series, nearby city, distance, climb, tags and month.
list_race_filtersReadThe exact filter values (race kinds, countries, series, climb, tags, months) the search accepts.
get_raceReadOne race in full: dates, events with distance and climb, venue, course and results, with a link to its page. Sections narrow it to the part you asked about.
save_raceWriteAdd races found by search to your list; duplicates are reported, not repeated.
add_custom_raceWriteAdd a race the search does not list, with a name, date and optional place and link. An unannounced date goes in as your guess, not as a fact.
remove_raceWriteTake a race off your list; training sessions stay.
get_tripReadOne race on your list in depth: the race, the sessions between now and race day, the notes linked to it, and on request your saved plans, the nearest airports, places to stay (affiliate links to Stay22) and race-day weather.
save_trip_planWriteKeep what you planned for a race, one section at a time: race plan, fuelling, gear checklist, travel notes, where you are staying. Saving a section again replaces it.
add_training_planWritePut a whole training plan from the library on your calendar, ending on your race day or starting on a Monday you pick.
add_noteWriteSave a diary note on a date, in your own words: how the body feels, what the physio said, a course recce.
update_noteWriteAdd to a note or change its date, title, tags or links.
delete_noteWriteDelete a diary note.
get_notesReadRead the diary: one note by id, a keyword search with snippets, or the newest notes in a date range.
add_blockWritePut a training block on the calendar: a named stretch of weeks with one goal. Blocks can run alongside each other; one is the day's main block.
update_blockWriteRename a block, move or extend its weeks, rewrite its goal or notes, switch it between main and alongside.
remove_blockWriteTake a training block off the calendar. Every session in those weeks stays.
get_blocksReadYour training blocks with their dates and goals; the ones covering today say which week of the block you are in.
get_profileReadYour home city, time zone, units, the kinds of race you look for and how far you will travel.
update_profileWriteChange your home city, time zone, units, the kinds of race you look for or how far you will travel.

Data handling

  • What we store: your account email, the races on your list, your training sessions and diary notes, the plans you save for a race, and your profile: home city, time zone, units and the kinds of race you look for.
  • What we log per tool call: the tool name, the parameters the assistant sent, how long the call took and any error, for product analytics.
  • What we do not log: what a tool returns, such as your calendar, is not sent to analytics.
  • Affiliate links: when you ask where to stay for a race, get_trip returns links to Stay22. They are affiliate links and each one is marked affiliate: true: Goal Race may earn a commission if you book, at no extra cost to you. The link carries the race location, the race dates and our partner ID, and nothing about you. No other tool returns sponsored content.
  • Third parties a tool calls: for race-day weather, get_trip sends the place and date of the race to Open-Meteo. No account data goes with it.
  • Where: data is stored in the EU.
  • Deletion: delete your account in Settings, or email support@goalrace.com .

The full policy is in the Privacy Policy .

Rate limits and errors

Failures are returned as JSON-RPC 2.0 error objects with a numeric code and a message: -32700 parse error, -32600 invalid request, -32601 method not found, -32602 invalid parameters and -32603 internal error. A tool that cannot do what was asked, for example an unknown session ID, returns a message the assistant can read and act on.

When the access token is missing, invalid or expired, the server answers 401 with a WWW-Authenticate header that points to the protected-resource metadata above, so a compliant client starts the sign-in flow or refreshes its token on its own. There is no published per-user quota; normal assistant use is well within what the server handles.

Support

Questions or problems: support@goalrace.com . See also the Privacy Policy and the Terms of Service .