Use your scores, target races and results in conversations with your AI. You do not need to buy an API key for this connection. Your AI service’s own subscription and usage terms still apply.
Server address
https://trailstatus.jp/mcp
Claude
Add a custom connector in Claude and enter the server address above.
Copy a question into your connected AI. Ask it to check freshness and missing data, and separate facts from suggestions.
Strengths and gaps
Read my latest TRAIL STATUS summary. First check the calculation date and missing data. Explain my strengths, gaps and training priorities across the six axes. Distinguish measurements, estimated scores and carried-forward values. Separate facts from suggestions.
Prepare for my target race
Use TRAIL STATUS get_race_briefing to read my current target race, six axes, results and weekly plan. Check freshness, sharing scope and missing data. List three preparation priorities and three questions for me. A registered race alone does not prove participation.
Review a race
Use TRAIL STATUS get_race_review to list my results and ask which race I want to review. With that result ID, compare the result against a saved prediction for the matching edition. Explain possible improvements. If there is no matching saved prediction, say so; do not substitute a current prediction.
In the app, open Settings → Data & backup → AI connection to check clients, the calculation date and the server sync time. Check connection & settings loads the latest state; Sync summary updates the summary.
Choose categories for scores, races/results, training, injuries/subjective logs/HR, gear, other data and calibration. Save applies to all AI connections and is enforced by the server. Race results include race-day condition notes. Calibration data is returned only when all categories are shared. Data already received by an AI service cannot be recalled.
Disconnect a client to stop its current access and refresh tokens. Other AI connections and your Strava app connection remain active. Authorize again from your AI client to reconnect.
Reading the numbers
Scores are estimates derived from measurements. Carried-forward axes, unmeasured axes and calculation changes are identified. Summaries calculated seven or more days ago are marked for updating. A recent sync does not mean a recent calculation. Correlation does not establish causation.
After connecting
Open TRAIL STATUS while signed in with Strava and let it sync.
Enable this connection in your AI client and ask, for example, “Which of my six axes needs work, and what should I prioritize for my target race?”
If the summary is not ready yet, reopen the app and sync. Connecting does not require opting in to Help calibrate.
Data access and disconnecting
This is read-only access to your own synced inputs and summaries such as six-axis and overall scores. No tool changes your targets or results. Data received by your AI service is handled under its policies.
Revoke the client in the app’s AI connection settings and remove it in your AI client. Revoking TRAIL STATUS in Strava also disconnects the app itself.
This guide covers Claude and local Codex / Gemini CLI clients. Each user must authorize their own account. The Gemini web and mobile apps are not covered: Google applies regional, language and account requirements, and this server does not yet allow their web OAuth callback.